Re: PATH=/usr/local/bin:/bin:/usr/bin considered harmful

2012-07-01 Thread Reindl Harald
Am 22.06.2012 14:45, schrieb Sam Varshavchik: >> Well, yeah. But the Law of unintended consequences applies and that is why i cried out loud that the UsrMove has zero benfits in the real world and crying for troubles long ago before F17 was GA >> so we must be careful FESCo should HAVE BEEN a

Re: PATH=/usr/local/bin:/bin:/usr/bin considered harmful

2012-07-01 Thread Reindl Harald
Am 22.06.2012 13:26, schrieb Andrew Haley: > On 06/22/2012 12:10 PM, Reindl Harald wrote: >> >> Am 22.06.2012 13:07, schrieb Andrew Haley: >>> On 06/22/2012 11:44 AM, Sam Varshavchik wrote: Andrew Haley writes: > On 06/22/2012 04:15 AM, Sam Varshavchik wrote: >> The new perl pac

Re: PATH=/usr/local/bin:/bin:/usr/bin considered harmful

2012-06-23 Thread Björn Persson
These search path problems seem to be cropping up in lots of packages. Here's another example: https://bugzilla.redhat.com/show_bug.cgi?id=797557 GPRbuild is designed to be relocatable, because the corporations that are Adacore's customers want to be able to drop a directory tree with binaries

Re: PATH=/usr/local/bin:/bin:/usr/bin considered harmful

2012-06-23 Thread Sam Varshavchik
Roman Rakus writes: On 06/22/2012 05:15 AM, Sam Varshavchik wrote: [root@octopus ~]# strings /bin/bash | grep usr.bin /usr/local/bin:/bin:/usr/bin I think that bash needs to be recompiled, with the last two flipped, in the default shell PATH. The path above is used by bash only if PATH env

Re: PATH=/usr/local/bin:/bin:/usr/bin considered harmful

2012-06-23 Thread Roman Rakus
On 06/22/2012 05:15 AM, Sam Varshavchik wrote: [root@octopus ~]# strings /bin/bash | grep usr.bin /usr/local/bin:/bin:/usr/bin I think that bash needs to be recompiled, with the last two flipped, in the default shell PATH. The path above is used by bash only if PATH env variable is not set.

Re: PATH=/usr/local/bin:/bin:/usr/bin considered harmful

2012-06-23 Thread Michael Schwendt
On Fri, 22 Jun 2012 18:16:03 -0400, Sam Varshavchik wrote: > Michael Schwendt writes: > > > > > # whereis ldconfig > > ldconfig: /sbin/ldconfig /usr/sbin/ldconfig > > /usr/share/man/man8/ldconfig.8.gz > > > > /sbin is before /usr/sbin in $PATH. > > Only for root. And not affecting "whereis" bu

Re: PATH=/usr/local/bin:/bin:/usr/bin considered harmful

2012-06-22 Thread Sam Varshavchik
Michael Schwendt writes: # whereis ldconfig ldconfig: /sbin/ldconfig /usr/sbin/ldconfig /usr/share/man/man8/ldconfig.8.gz /sbin is before /usr/sbin in $PATH. Only for root. rpm stuff does not get built as root. pgp3Q8qbqlldX.pgp Description: PGP signature -- devel mailing list devel@li

Re: PATH=/usr/local/bin:/bin:/usr/bin considered harmful

2012-06-22 Thread John Ellson
> Having thought about it, I don't think it's unreasonable to do a "which $PROG", and stick it into the hashbang. I think that's a perfectly reasonable approach, with portability being the goal. The problem I see here, is > that Fedora's bash is compiled with the default PATH placing a symlink,

Re: PATH=/usr/local/bin:/bin:/usr/bin considered harmful

2012-06-22 Thread Richard W.M. Jones
On Fri, Jun 22, 2012 at 03:08:05PM +0100, Richard W.M. Jones wrote: > A similar issue is that whenever anyone uses AC_PATH_PROG or related > in a configure script anywhere, it finds the /bin binary ahead of > /usr/bin. Maybe I mean this the other way around. Rich. -- Richard Jones, Virtualizati

Re: PATH=/usr/local/bin:/bin:/usr/bin considered harmful

2012-06-22 Thread Richard W.M. Jones
A similar issue is that whenever anyone uses AC_PATH_PROG or related in a configure script anywhere, it finds the /bin binary ahead of /usr/bin. You get odd-looking output from ./configure, and perhaps other problems too (though I haven't seen any specifically). Rich. -- Richard Jones, Virtual

Re: PATH=/usr/local/bin:/bin:/usr/bin considered harmful

2012-06-22 Thread Michael Schwendt
On Fri, 22 Jun 2012 06:53:09 -0400, Sam Varshavchik wrote: > Michael Schwendt writes: > > > On Fri, 22 Jun 2012 09:50:25 +0100, Mary Ellen Foster wrote: > > > > > I assume this error is also an instance of the same problem: > > > > > > Error: Package: 2:samba-common-3.6.5-89.fc17.1.x86_64 (@upda

Re: PATH=/usr/local/bin:/bin:/usr/bin considered harmful

2012-06-22 Thread Andrew Haley
On 06/22/2012 01:45 PM, Sam Varshavchik wrote: > Andrew Haley writes: > >> On 06/22/2012 01:19 PM, Sam Varshavchik wrote: >>> Andrew Haley writes: >>> > Why not take /bin and /sbin out of the default path *and* make sure > that RPM knows about /bin/* ? >>> I would expect that changing rpm

Re: PATH=/usr/local/bin:/bin:/usr/bin considered harmful

2012-06-22 Thread Sam Varshavchik
Andrew Haley writes: On 06/22/2012 01:19 PM, Sam Varshavchik wrote: > Andrew Haley writes: > >> > Why not take /bin and /sbin out of the default path *and* make sure >> > that RPM knows about /bin/* ? > I would expect that changing rpm will be a long, tedious process. Which is > understandable.

Re: PATH=/usr/local/bin:/bin:/usr/bin considered harmful

2012-06-22 Thread Andrew Haley
On 06/22/2012 01:19 PM, Sam Varshavchik wrote: > Andrew Haley writes: > >> > Why not take /bin and /sbin out of the default path *and* make sure >> > that RPM knows about /bin/* ? > I would expect that changing rpm will be a long, tedious process. Which is > understandable. > > But changing the

Re: PATH=/usr/local/bin:/bin:/usr/bin considered harmful

2012-06-22 Thread Sam Varshavchik
Andrew Haley writes: Why not take /bin and /sbin out of the default path *and* make sure that RPM knows about /bin/* ? I would expect that changing rpm will be a long, tedious process. Which is understandable. But changing the default PATH that's compiled into bash should be a simpler ch

Re: PATH=/usr/local/bin:/bin:/usr/bin considered harmful

2012-06-22 Thread Andrew Haley
On 06/22/2012 12:10 PM, Reindl Harald wrote: > > Am 22.06.2012 13:07, schrieb Andrew Haley: >> On 06/22/2012 11:44 AM, Sam Varshavchik wrote: >>> Andrew Haley writes: >>> On 06/22/2012 04:15 AM, Sam Varshavchik wrote: > The new perl package contains /usr/bin/perl. At upgrade, dependency

Re: PATH=/usr/local/bin:/bin:/usr/bin considered harmful

2012-06-22 Thread Andrew Haley
On 06/22/2012 11:44 AM, Sam Varshavchik wrote: > Andrew Haley writes: > >> On 06/22/2012 04:15 AM, Sam Varshavchik wrote: >>> The new perl package contains /usr/bin/perl. At upgrade, dependency >>> resolution is not smart enough to realize that the new package's >>> /bin/perl=/usr/bin/perl, causin

Re: PATH=/usr/local/bin:/bin:/usr/bin considered harmful

2012-06-22 Thread Sam Varshavchik
Michael Schwendt writes: On Fri, 22 Jun 2012 09:50:25 +0100, Mary Ellen Foster wrote: > I assume this error is also an instance of the same problem: > > Error: Package: 2:samba-common-3.6.5-89.fc17.1.x86_64 (@updates-testing) >Requires: /usr/sbin/ldconfig >Removing: gli

Re: PATH=/usr/local/bin:/bin:/usr/bin considered harmful

2012-06-22 Thread Sam Varshavchik
Andrew Haley writes: On 06/22/2012 04:15 AM, Sam Varshavchik wrote: > The new perl package contains /usr/bin/perl. At upgrade, dependency > resolution is not smart enough to realize that the new package's > /bin/perl=/usr/bin/perl, causing a conflict. What exactly is the conflict? See the err

Re: PATH=/usr/local/bin:/bin:/usr/bin considered harmful

2012-06-22 Thread Michael Schwendt
On Fri, 22 Jun 2012 09:50:25 +0100, Mary Ellen Foster wrote: > I assume this error is also an instance of the same problem: > > Error: Package: 2:samba-common-3.6.5-89.fc17.1.x86_64 (@updates-testing) >Requires: /usr/sbin/ldconfig >Removing: glibc-2.15-37.fc17.i686 (@fedo

Re: PATH=/usr/local/bin:/bin:/usr/bin considered harmful

2012-06-22 Thread Mary Ellen Foster
On 22 June 2012 09:39, Juan Orti Alcaine wrote: > 2012/6/22 Sam Varshavchik : > > I think that bash needs to be recompiled, with the last two flipped, in > the > > default shell PATH. > > > > I have hit a similar issue with the tor-arm package. It is executed by > a wrapper script that check if i

Re: PATH=/usr/local/bin:/bin:/usr/bin considered harmful

2012-06-22 Thread Juan Orti Alcaine
2012/6/22 Sam Varshavchik : > I think that bash needs to be recompiled, with the last two flipped, in the > default shell PATH. > I have hit a similar issue with the tor-arm package. It is executed by a wrapper script that check if it has been called with /usr/bin/arm, but because the path orderin

Re: PATH=/usr/local/bin:/bin:/usr/bin considered harmful

2012-06-22 Thread Andrew Haley
On 06/22/2012 04:15 AM, Sam Varshavchik wrote: > The new perl package contains /usr/bin/perl. At upgrade, dependency > resolution is not smart enough to realize that the new package's > /bin/perl=/usr/bin/perl, causing a conflict. What exactly is the conflict? Andrew. -- devel mailing list d

PATH=/usr/local/bin:/bin:/usr/bin considered harmful

2012-06-21 Thread Sam Varshavchik
The perl update that hit updates this week is causing a yum conflict with some locally-built packages, of this type: Error: Package: courier-imap-4.10.0.20120202-2.17.x86_64 (installed) Requires: /bin/perl Removing: 4:perl-5.14.2-211.fc17.x86_64 (@anaconda-0) N