Thu 14 Sep 2006 05:46:40 PM UTC, comment #4:
> Your implementation works fine, but isnt' there a way to
> sourceinstall discover by itself which is the default prefix
> from the source?
Yes, but the question is: is it a good idea?
By using a global default prefix option, the user can be sure that all packages he installs have a certain prefix, when he does not explicitly override the globally defined default.
Otherwise we are left with the packager's whims
(Is it /usr/local, /usr, $HOME/name, /usr/local/name, ...),
which means that after installing X packages we might have X different prefixes, with the involved confusion and potential necessity to extend PATH, LD_LIBRARY_PATH, PKG_CONFIG_PATH, YOUR_PATH_HERE,...
while by forcing the default prefix option we gain uniformity and simplicity.
It could be possible to show the package-provided prefix in the Directories tab as a reference though.
By the way, all packages installed from source code should have a package-provided default prefix of /usr/local (GNU coding standards, Filesystem Hierarchy Standard), so I do not agree with the samba choice here.
FHS:
http://www.pathname.com/fhs/pub/fhs-2.3.html#USRLOCALLOCALHIERARCHY
|