Handling Typical Installations
I just had a (brilliant, IMNSHO :-) idea on how we can easily handle
typical installations and not require any changes to dpkg/dselect.
We simply create a new section (let's call it "typical" for now) and
populate it with dummy packages that don't contain any files but
depend on the desired set of real packages. For example, we could
have a "c-devel" package which depends on binutils, gcc and libc6-dev,
or a "web-server" package which depends on apache and whatever else is
needed. This approach has the additional advantage that dependencies
for new packages could be easily added to the dummy packages and they
would be automatically selected the next time the user upgrades.
As stated before, this approach doesn't require any changes to
dselect. However, we might want to make a few minor changes anyway.
One example would be to give "typical" packages preferential treatment
like making sure they are listed first when dselect is run the first
time.
What do y'all think?
David
--
David Engel ODS Networks
david@sw.ods.com 1001 E. Arapaho Road
(972) 234-6400 Richardson, TX 75081
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
debian-devel-request@lists.debian.org .
Trouble? e-mail to templin@bucknell.edu .
Reply to: