On Sun, 8 Mar 2009 17:35:27 +0100
Raphael Hertzog <[email protected]> wrote:

> In the transition period, dpkg will likely depend on the package providing
> install-info. But the long term goal is surely to decouple this from dpkg
> and have scripts not assume anything about its availability. But this
> could be moot sooner if we implement what I suggested below.
> 
> > > I would really suggest that you design a solution that doesn't require
> > > the postinst snippet at all. A simple solution could be:
> > > - have a package "install-info" register a file trigger on 
> > > /usr/share/install-info/
> > > - have other packages provide a .install-info file in that directory that
> > >   tells how install-info should be called
> > > - add a dh_installinfo helper to automatize the installation of this file
> > > - have info readers depend on the new install-info package
> > > 
> > > Opinions ?
> > 
> > One thing I cannot do is modify the relevant debian/rules of the
> > packages concerned because Grip does not rebuild any packages, in order
> > to retain binary compatibility with Debian.
> 
> This "solution" is not for Emdebian, it's for Debian as a whole. So you
> would not have to modify anything.

OK, sorry for the misunderstanding.

Do we know how many packages use info documents?
$ ls /usr/share/info/*.gz -1|xargs dpkg -S|cut -d':' -f1 |sort -u|wc -l
45
that's just on this system.

I've had a quick look via UDD but I can't see how the existing table
structures can provide information on what packages do in postinst
scripts.

The initial set would be (based on a Lenny debootstrap):

Clint Adams <[email protected]>
   cpio
   sed

Eric Dorland <[email protected]>
   automake1.10
   automake1.7

Bdale Garbee <[email protected]>
   gzip

LaMont Jones <[email protected]>
   util-linux

Matthias Klose <[email protected]>
   readline5

Noèl Köthe <[email protected]>
   wget

Steve Langasek <[email protected]>
   nano (U)

Chuan-kai Lin <[email protected]>
   findutils (U)

Jordi Mallach <[email protected]>
   nano

Andreas Metzler <[email protected]>
   findutils

Michael Stone <[email protected]>
   coreutils

Santiago Vila <[email protected]>
   gettext
   m4

Martin Zobel-Helas <[email protected]>
   ed

If a simple debootstrap works without info documents, it makes it a lot
easier to manage because workarounds don't need to be forced into the
debootstrap stage but can be handled afterwards.

Still, it would appear to be a reasonable size transition - I don't
have the time to push the entire thing. All I want is for install-info
to not get in the way of the installations.

-- 


Neil Williams
=============
http://www.data-freedom.org/
http://www.linux.codehelp.co.uk/
http://e-mail.is-not-s.ms/

Attachment: pgpHMhgiN4t4f.pgp
Description: PGP signature

Reply via email to