Re: Why 2 inconsistent package managers frontents?
On Mon, 19 Jun 2000, Joey Hess wrote:
> Jason Gunthorpe wrote:
> > Where is the documentation that says anything but dselect methods update
> > the available file?
> Ahem, dpkg(1):
> dpkg --update-avail | --merge-avail Packages-file
> Update dpkg's and dselect's idea of which packages
> are available.
Thats 'how' not 'when'. One of the dpkg manuals describes how the dselect
methods work and it boils down to using the *-avail functions in the
update script. Dats it.
> > Remember, way long ago apt-get had to co-exist with a
> > non-apt dselect method so doing this update automatically would have been
> > quite bad.
> I don't really understand why. Isn't the dpkg ststus area locked when
> the available file is being merged?
Locking isn't the issue. If dselect is not using apt as the access method
then apt has no right to blow away the available file. The available file
is first and formost for use by dselect [in truth, any libdpkg based UI]
to communicate with the access method.