> Subject: Re: Bug#18567: 18567 -- bug or feature? > From: Thomas Hood <[EMAIL PROTECTED]> > To: Paul Vojta <[EMAIL PROTECTED]> > Cc: [EMAIL PROTECTED] > Date: 10 Oct 2002 09:54:58 +0200 > > On Wed, 2002-10-09 at 20:17, Paul Vojta wrote: > > > Being able to set the PATH for dpkg might be considered > > > a feature, not a bug. > > > > Only if it's done intentionally. > > E.g.: bash% DPKG_PATH=... dpkg -i foobar.deb > > dpkg can't know how the path was set.
Please look at my example again. Of course, dpkg can't know how the environment variable DPKG_PATH was set, either, but it's more forgivable for dpkg to act on environment variables if they begin with the characters DPKG_. IMHO, it would be better for dpkg to set its own path. If people want to set the path for dpkg to use (e.g., for testing), then dpkg should provide a way to do this, such as: (1) a command-line option, (2) an environment variable *specific to dpkg*, or (3) a configuration file. > Still, I think you are right that the packaging system > should be able to find its own components when the > user sets the PATH. --Paul Vojta, [EMAIL PROTECTED]
