Orn E. Hansen wrote: > > What Im driving at is... for a writer, make an environment > suitable for writers... and for an office worker set up an > environment for an office worker... each can be based on a > common os... but to try and create a one setup to serve > all... will only fail (unless you're going for a > guaranteed ten years service part :-) > Proposal: While watching the discussion concerning dselect that went on a while back it occured to me the deselect may not be the best place to implement "role based system configuration" (a setup based on what the intended user will be doing). It seems to me that dpkg should (already) support recursive packages. That is, the install(remove) script for a package would invoke dpkg to install(remove) other packages as well as modify config(and .*rc) files. And, rather than just making suggestions about how to improve dselect it would be easy enough to constuct a role based package and say 'see like this'. My current configuration is nothing to brag about, but I would like to see what the experts have done. The main benefit would be to allow an installer to invoke dpkg once(few) times on a(some) role based package(s).
1) is this possible? 2) if so, how would it be done? 3) does anyone out there feel that their setup is exemplary? (given a particular role) 4) assuming positive answers on the previous; I think such packages would be best suited for "admin". 5) would it be possible to generate a role package automagically from the dpkg status files? Thanks, from a gnubie -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
