From: Alexandre Buisse <nattfodd@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: Re[2]: [gentoo-dev] manpages that requires dependencies
Date: Fri, 25 Nov 2005 11:21:20 +0100 [thread overview]
Message-ID: <41b037ed0511250221v43808415hf0b77b50b05c1624@mail.gmail.com> (raw)
In-Reply-To: <484811244.20051125081301@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 2050 bytes --]
On 11/25/05, Jakub Moc <jakub@gentoo.org> wrote:
>
>
> 25.11.2005, 0:58:28, Ciaran McCreesh wrote:
>
> > On Fri, 25 Nov 2005 00:49:23 +0100 "Diego 'Flameeyes' Petteno"
> > <flameeyes@gentoo.org> wrote:
> > | Hi everybody, a little question that I'd like to be answered (so that
> > | we can make it a sort of rule).
> > | How should manpages that are generated be managed?
> > |
> > | The common sense and looking to other ebuilds would say to always
> > | build man pages, but when it asks me to install something like
> > | docbook-sgml-utils, I'm tempted not to do that ;)
>
> > man pages can't be considered optional (despite what RMS says). They're
> > not fancy extra HTML API documentation, they're core, so they don't get
> > a USE flag.
>
> > Of course, if FEATURES were in the USE expand list, you could use
> > ! features_noman ? ( ) ...
>
> That is all fine and dandy, but if you search bugzilla for USE=doc related
> bugs, you might think twice before adding yet another inevitably broken
> thing
> to portage. docbook-sgml-utils & co. is extremely fragile and buggy thing.
Actually, every automated text generation tool seems to be extremely fragile
and buggy, see gtkdoc for instance, which also regularly breaks USE=doc.
About manpages, I agree that they are non-optional and should be provided
all the time, which leads us straight to the solution : have the
maintainer/ebuild writer generate once the manpages (they shouldn't depend
on anything on the host machine, right ?) and provide them either directly
in the portage tree, as many are under the 20K limit, or as a tarball in
distfiles. If the developer hasn't docbok-sgml-utils and doesn't want to
pollute his system with it, he could ask text-markup, for instance, to
generate the manpages for him.
Of course, this doesn't solve the problem of manpages whose content is not
the same everywhere (but are there some of these ? Or may be all of them are
and I completely missed the point of this thread ?)
Regards,
Alexandre
[-- Attachment #2: Type: text/html, Size: 2471 bytes --]
next prev parent reply other threads:[~2005-11-25 10:25 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-24 23:49 [gentoo-dev] manpages that requires dependencies Diego 'Flameeyes' Pettenò
2005-11-24 23:58 ` Ciaran McCreesh
2005-11-25 0:03 ` Diego 'Flameeyes' Pettenò
2005-11-25 7:13 ` Re[2]: " Jakub Moc
2005-11-25 10:21 ` Alexandre Buisse [this message]
2005-11-25 10:46 ` Marius Mauch
2005-11-25 18:52 ` Mike Frysinger
2005-11-27 9:21 ` Kevin F. Quinn
2005-11-27 12:58 ` Ned Ludd
2005-11-27 13:09 ` Ned Ludd
2005-11-27 14:39 ` Jason Stubbs
2005-11-27 14:43 ` Re[2]: " Jakub Moc
2005-11-27 15:05 ` Jason Stubbs
2005-11-27 15:48 ` Jason Stubbs
2005-11-27 16:12 ` Ned Ludd
2005-11-27 16:28 ` Mike Frysinger
2005-11-27 16:48 ` Ned Ludd
2005-11-27 16:45 ` Diego 'Flameeyes' Pettenò
2005-11-27 14:47 ` Ned Ludd
2005-11-27 14:50 ` Diego 'Flameeyes' Pettenò
2005-11-27 15:01 ` Jason Stubbs
2005-11-27 15:43 ` Jason Stubbs
2005-11-27 16:49 ` Ciaran McCreesh
2005-11-27 17:30 ` Diego 'Flameeyes' Pettenò
2005-11-25 16:43 ` Michael Cummings
2005-11-25 19:27 ` Ciaran McCreesh
2005-11-25 16:52 ` Jason Stubbs
2005-11-25 19:27 ` [gentoo-dev] " Duncan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=41b037ed0511250221v43808415hf0b77b50b05c1624@mail.gmail.com \
--to=nattfodd@gmail.com \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox