Are there several issues here? The package maintainer has the package to worry about. Another "hat" might wrap packages for installers, including templates for a variety of sources (like RPMs, the FreeBSD ports collection, etc). The last "hat" would take these packages, possibly build them, and then install them according to the local paradigm. In fact, this last "hat" might well package (parts?) of things up one more time, for unpackaging on a per-user basis. I have to do this at one site that does automated testing. An example of this last case is apache, which gets installed in a version-specific subdirectory and then each test user gets a small subdir in their home directory that contains an httpd.conf file (with a per-user port for the webserver) and a customized start/stop script. H
- Re: More an autopackage Tom Tromey
- Re: More an autopackage Geoffrey Wossum
- Re: More an autopackage Derek R. Price
- Re: More an autopackage Harlan Stenn
- Re: More an autopackage Tom Tromey
- Re: More an autopackage Derek R. Price
- RE: More an autopackage Bernard Dautrevaux
- Re: More an autopackage Geoffrey Wossum
- Re: More an autopackage Derek R. Price
- Re: More an autopackage Michael Sweet
- Re: More an autopackage Harlan Stenn
- Re: More an autopackage Pavel Roskin
- Re: More an autopackage Raja R Harinath
- Re: More an autopackage Michael Sweet
- Re: More an autopackage Rusty Ballinger
- Re: More an autopackage Michael Sweet
- Re: More an autopackage Steve Robbins
- Re: More an autopackage Geoffrey Wossum
- Re: More an autopackage Derek R. Price
- Re: More an autopackage Harlan Stenn
- Re: More an autopackage Derek R. Price