From: Mamoru KOMACHI <usata@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] *-doc vs USE="doc"
Date: Sat, 12 Jul 2003 20:53:21 +0900 [thread overview]
Message-ID: <86n0fk7yha.wl@rico.usata.org> (raw)
In-Reply-To: <1057999358.30632.25.camel@mcvaio.liquidx.net>
Hi,
At 12 Jul 2003 09:42:39 +0100,
Alastair Tse wrote:
> Also, it seems to me that the "doc" USE flag is too encompassing. It is
> used for both installing user documentation (user guides, application
> user help) and also to install developer documentation (APIs,
> programming tutorials, Javadoc, etc). I think we should have a "devdoc"
> USE flag to differentiate between the two.
I agree. It would be better to turn on/off doc installation with "doc"
USE flag (even though it is a user documentation, some may not want to
install any documentation at all).
Also I suggest that we would better have "man" USE flag to decide
whether we will install man pages or not (defaults to turn on).
However, this "man" USE flag raises one question -- how should we deal
with i18n man pages? I've almost translated portage man into Japanese,
but don't know where to ask. I think there are three options:
1. put it into app-i18n/manpages-ja, together with other Japanese
man pages
2. create app-i18n/gentoo-manpages-ja and put portage (and possibly
gentoolkit) man pages into it
3. put it into sys-apps/portage and create <lang> USE flag to
determine which man pages to install
The problem in the first option is that if we install manpages-<lang>,
we have to install all the man pages in it regardless of what
applications we use (eg. we have to install NIS/NFS man pages even when
we don't install them). Currently German, Spanish, French and Russian
have their own man pages in app-i18n, but none of them has portage
man pages translated.
And if we take the second option (originally nakano suggested me this
option) we will have both manpages-ja and gentoo-manpages-ja, which,
in my point of view, does not look nice. However, if we separate
gentoo-manpages-<lang> from manpages-<lang>, we can keep
gentoo-manpages-<lang> up to date pretty easily.
Lastly, if we are to have <lang> USE flag and "man" USE flag, we
should modify /usr/lib/portage/bin/*man to handle i18nised man pages.
If we have USE="ja man", Japanese man pages will be installed in
addition to standard man pages. I think this is the most "gentooish" way
of dealing with i18n, but the problem is we need to split
manpages-<lang> into individual ebuilds. Of course it takes a lot of
time and efforts, and it will get complicated to manage i18n man pages
(though we needn't care about it in each ebuild, as it is hidden in
portage helper scripts shown above). Suppose there is an update of
translated man pages but no change in original source, should we change
the revision number so that people who turn the USE flag on can get
the benefit of it (the most non-<lang> speaker will not get any
advantage from it but be forced to recompile it) ?
Any comments?
regards,
--
Mamoru KOMACHI <usata@gentoo.org>
--
gentoo-dev@gentoo.org mailing list
prev parent reply other threads:[~2003-07-12 11:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-12 8:42 [gentoo-dev] *-doc vs USE="doc" Alastair Tse
2003-07-12 10:25 ` Spider
2003-07-12 14:49 ` Alastair Tse
2003-07-12 15:22 ` Peter Ruskin
2003-07-12 11:53 ` Mamoru KOMACHI [this message]
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=86n0fk7yha.wl@rico.usata.org \
--to=usata@gentoo.org \
--cc=gentoo-dev@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