Re: IMPORTANT: What can we do about the base package?
'Joey Hess wrote:'
>> The main problem is the device files in /dev. These are created by the
>> makedev package, but are not in its file list. They _are_ in base's
>> file list, so removing base is a bad thing to do without a great deal
>> of care.
>> Would it be possible to incorporate a really gross hack into makedev
>> that `manually' removes the base package (so long as base-files and
>> base-passwd are installed) without dpkg getting involved (i.e. by
>> removing its files from /var/lib/dpkg/info and editing
>> /var/lib/dpkg/status)? This idea will probably give Ian a fit...
>How about releasing an update of the base package that contains no files,
>but instead runs MAKEDEV to generate the files in /dev? Then after you
>install it, you can unistall it safely, without killing /dev.
What happens if it gets installed before base-passwd or base-files?
Christopher J. Fearnley | Linux/Internet Consulting
email@example.com, firstname.lastname@example.org | UNIX SIG Leader at PACS
http://www.netaxs.com/~cjf | (Philadelphia Area Computer Society)
ftp://ftp.netaxs.com/people/cjf | Design Science Revolutionary
"Dare to be Naive" -- Bucky Fuller | Explorer in Universe