Well, it won't probably answer the questions of any one, but for the
"package" I'm working on, these are true:
1) Compilation is a separate step (One can cross compile on a MATRIX for
a distinct TARGET).
2) Sources are read-only and the compilation is done elsewhere.
3) Space requirements are low since the framework knows how to remove
intermediate products on the run if needed. (I was tired to compile
things that need 2 Gig to end installing 200 Mega---NetBSD comes to
mind; gcc the same etc.)
4) Once compilation is done, you create a package that is simply a
tarball with the stuff that needs to be installed, a script and a _map_
that tells : this thing here shall be put there, with owner: owner:group
and permissions: permissions.
5) The map is generally relative to a $TARGETOPTDIR that one can set as
one wants. User can also just provide another completely different map
if one wants.
Conclusion: it should be relatively easy for anyone to end with the
stuff where one wants.
There will be a default:
a) If there is some kind of majority.
b) If not, conform to where _I_ want to install for my own personal
use ;)
--
Thierry Laronde (Alceste) <tlaronde +AT+ polynum +dot+ com>
http://www.kergis.com/
Key fingerprint = 0FF7 E906 FBAF FE95 FD89 250D 52B1 AE95 6006 F40C
