Daniel Macks wrote:
[]
> The messages are quite literal in what is missing: you need to add a
> START-INFO-DIR-ENTRY block or a "This file documents" paragraph to
> gengetopt.info.
Should we really need to hack GNU-supplied GNU info files?
Something isn't right there. I haven't followed the histo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
So I should likely wait till we come up with a policy for how fink
will handle this?
- ---
TS
http://southofheaven.org/
Chaos is the beginning and end, try dealing with the rest.
On 22-Aug-06, at 1:42 AM, Martin Costabel wrote:
> Daniel Macks wrote
On Tue, Aug 22, 2006 at 09:42:34AM +0200, Martin Costabel wrote:
> Daniel Macks wrote:
> []
> > The messages are quite literal in what is missing: you need to add a
> > START-INFO-DIR-ENTRY block or a "This file documents" paragraph to
> > gengetopt.info.
>
> Should we really need to hack GNU-sup
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Also it seems that our install-info is out of date from debian's,
maybe we should update ours?
- ---
TS
http://southofheaven.org/
Chaos is the beginning and end, try dealing with the rest.
On 22-Aug-06, at 9:57 AM, Daniel Macks wrote:
> On Tue, Aug
The concept of versioning in dpkg's install-info appears to have no
meaning...when dpkg is built, it patches its own version string into
install-info. So "dpkg x.y.z supplies install-info x.y.z" always, and
says nothing about the features or changes within install-info.
The install-info in the lat
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
well was an idea :P Just want to get the new gengetopt out :P Shall
I just comment out the InfoDocs: field for now?
- ---
TS
http://southofheaven.org/
Chaos is the beginning and end, try dealing with the rest.
On 22-Aug-06, at 10:58 AM, Daniel Mac