| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
gcc-3.4*, as it's known to break GNUstep apps
|
|
|
|
| |
to this, we will chmod them.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
checking for the portage version. So there is now no more portageq usage
in "global scope". Tested with both portage 2.0.50-r11 and 2.0.51_rc1.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
by SPLIT_SPECS="true" in a gcc-compiler ETYPE ebuild
|
| |
|
|
|
|
| |
many changes to the gcc chunks after this.
|
| |
|
| |
|
|
|
|
| |
breakage if you have files in your cwd such as "q", "t", etc
|