Skip Menu |

This queue is for tickets about the Glib-Object-Introspection CPAN distribution.

Report information
The Basics
Id: 125154
Status: stalled
Priority: 0/
Queue: Glib-Object-Introspection

People
Owner: XAOC [...] cpan.org
Requestors: oldtechaa [...] gmail.com
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: (no value)



Subject: No man page for perli11ndoc
Date: Sat, 21 Apr 2018 01:34:33 +0000
To: bug-Glib-Object-Introspection [...] rt.cpan.org
From: oldtechaa <oldtechaa [...] gmail.com>
perli11ndoc has no man page. I filed a bug on the Debian package about a different topic [1] and a discussion ensued about Debian requiring a man page. It seems that in order to keep perli11ndoc in $PATH in Debian, it really should have a man page. I have no experience in writing man pages, although I do have experience writing docs, but I can write the man page if no one else would like to. Let me know. oldtechaa [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891334
On Fri Apr 20 21:34:54 2018, oldtechaa@gmail.com wrote: Show quoted text
> perli11ndoc has no man page. I filed a bug on the Debian package about a > different topic [1] and a discussion ensued about Debian requiring a man > page. It seems that in order to keep perli11ndoc in $PATH in Debian, it > really should have a man page. > > I have no experience in writing man pages, although I do have experience > writing docs, but I can write the man page if no one else would like to.
You don't need to write a manpage, you can submit a patch against perli11ndoc that adds POD documentation, and the POD can be converted to nroff and installed as a manpage as part of the install process. This is how a majority of the Perl modules on CPAN/in core Perl have manpages, they're all converted from POD. Thanks, Brian
Subject: Re: [rt.cpan.org #125154] No man page for perli11ndoc
Date: Sat, 21 Apr 2018 11:22:38 +0000
To: bug-Glib-Object-Introspection [...] rt.cpan.org
From: oldtechaa <oldtechaa [...] gmail.com>
I'll try to get it in by the next release deadline. I assume the conversion to nroff is something a Debian Perl maintainer should be familiar with? Otherwise, I can look into it and submit a patch for them. Thanks, oldtechaa On Sat, Apr 21, 2018, 12:59 AM Brian Manning via RT < bug-Glib-Object-Introspection@rt.cpan.org> wrote: Show quoted text
> <URL: https://rt.cpan.org/Ticket/Display.html?id=125154 > > > On Fri Apr 20 21:34:54 2018, oldtechaa@gmail.com wrote:
> > perli11ndoc has no man page. I filed a bug on the Debian package about a > > different topic [1] and a discussion ensued about Debian requiring a man > > page. It seems that in order to keep perli11ndoc in $PATH in Debian, it > > really should have a man page. > > > > I have no experience in writing man pages, although I do have experience > > writing docs, but I can write the man page if no one else would like to.
> > You don't need to write a manpage, you can submit a patch against > perli11ndoc that adds POD documentation, and the POD can be converted to > nroff and installed as a manpage as part of the install process. This is > how a majority of the Perl modules on CPAN/in core Perl have manpages, > they're all converted from POD. > > Thanks, > > Brian > > >
Stalling ticket until POD documentation is written for 'perli11ndoc'
Subject: Re: [rt.cpan.org #125154] No man page for perli11ndoc
Date: Wed, 21 Oct 2020 14:19:44 -0400
To: bug-Glib-Object-Introspection [...] rt.cpan.org
From: oldtechaa <oldtechaa [...] gmail.com>
Sorry for the delay. I have not forgotten about this and I do still intend to work on it. On Wed, Oct 21, 2020 at 1:44 PM Brian Manning via RT < bug-Glib-Object-Introspection@rt.cpan.org> wrote: Show quoted text
> <URL: https://rt.cpan.org/Ticket/Display.html?id=125154 > > > Stalling ticket until POD documentation is written for 'perli11ndoc' >
On Wed Oct 21 14:20:13 2020, oldtechaa@gmail.com wrote: Show quoted text
> Sorry for the delay. I have not forgotten about this and I do still intend > to work on it.
Okay, thanks for letting us know. Stalling ticket again until POD documentation is written for 'perli11ndoc'