> Well, as a user of Debian, i have a "quick hack" suggestion. One that > would seem to require minimal effort. Create a new section. call it > "configurations" or something like that. make it the section at the top > of dselect's list. inside this section will be a bunch of "dummy" .deb > files: webserver.deb, netclient.deb, ftpserver.deb, x.deb, etc... these > packages need contain nothing more than control files, which require (or > suggest) all the various components neccessary for that configuration. > > -brad I like this idea! (I've seen it before though) The nice part is that this is even nice for upgrades. If somebody chooses webserver - and a new apache module comes out, it could be added to the configuration package - and the user would automatically install it when they upgraded (via dselect). If somebody doesn't like the set of packages, they can always delete the configuration package and deviate. The only problem is that we now have to educate the users that they have to do this. It would be important to come up with sets of packages that don't conflict, I think. Because the quick install method is going to want to avoid the conflict resolution mechanism that dselect/diety will provide. Cheers, - Jim
Attachment:
pgp6oFLWLJQck.pgp
Description: PGP signature