On Wed, 2009-03-11 at 12:13:47 +0000, Neil Williams wrote: > What I really need, in order to test properly, is a package that can > trigger install-info. I admit, I'm a bit unfamiliar with triggers still > - what do I need to change in a package (say coreutils) that currently > contains an info document and maintainer script changes, in order to > test it with a trigger created by a patch to the experimental texinfo > sources above? > > Is it a case of: > 1. create debian/install-info.triggers in the tex source above > 2. create a modified coreutils (for testing in a chroot) where the info > document is part of the package, not mentioned in the maintainer > scripts > 3. and?
Neil, please hold your horses! Once dpkg provides the dummy install-info, then this is solved for you, and you don't have to do anything. Please check the transition plan on the wiki. Also: * As long as the new install-info packages is not installed on your system, then it won't be triggered. * Ideally we should not need any .install-info file, if we get the remaning incomplete Info files properly fixed. regards, guillem -- To UNSUBSCRIBE, email to debian-dpkg-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
