reassign 549011 safe-rm thanks Hi!
On Wed, 2009-09-30 at 12:09:04 +0200, Didier Raboud wrote: > Package: dpkg > Version: 1.15.4 > Severity: wishlist > I had safe-rm installed and perl broke (#548848). dpkg went unuseable because > it was using /usr/bin/rm from safe-rm, broken because of broken perl. > > So either safe-rm should be taken out of system PATH or dpkg should hardcode > the usage of /bin/rm (which this bugreport is about). One of the features of PATH is to allow the admin to override the system binaries. You had safe-rm installed and shot yourself in the foot when it broke, the same could have happened with coreutils (less probable though, but still). Programs should be able to rely on a functional rm to operate correctly (say, be able to remove stuff under /usr) w/o needing to hardcode the whole path, which safe-rm does not guarantee. That makes me think having safe-rm in the PATH at all is probably not a good idea anyway and I don't think we should be required to use hardcoded paths because safe-rm (or similar) might be there. At most safe-rm should explain its flakiness, as rm is a command that is Essential, and thus should always work, no matter what. Or yes, taken out of PATH and be used through aliases. Thus reassigning. regards, guillem -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
