| 1 |
If you haven't noticed, there was a change in baselayout-2.4 that |
| 2 |
moved the default PATH setting from /etc/profile into |
| 3 |
/etc/env.d/50baselayout. This change allows other packages to prepend |
| 4 |
or append their PATH settings by installing files before or after |
| 5 |
sequence 50 in /etc/env.d. See bug 255695. |
| 6 |
|
| 7 |
This has the immediate effect of moving the toolchain-related PATH |
| 8 |
settings (00glibc, 04gcc, 05binutils) to the left of the "default" |
| 9 |
system PATH. This wasn't necessarily intentional, but it should make |
| 10 |
for a minor performance improvement since gcc-wrapper is bypassed. I |
| 11 |
haven't noticed any problems. |
| 12 |
|
| 13 |
More generally, this change occurred a couple of months ago, and there |
| 14 |
doesn't appear to have been any major fallout in ~arch. However, bug |
| 15 |
629846 was opened today, which made the suggestion that we make a more |
| 16 |
public call for testing. |
| 17 |
|
| 18 |
So, if you maintain a package that installs a PATH setting in |
| 19 |
/etc/env.d, please check it to ensure that it is not causing conflicts |
| 20 |
with binaries that live in the default PATH. If needed, consider |
| 21 |
moving them to the right by choosing a number higher than 50. |
Archives