From: Mart Raudsepp <leio@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Changing doc use flag on gtk-doc packages to gtk-doc-rebuild or something else
Date: Tue, 07 Oct 2008 22:56:04 +0300 [thread overview]
Message-ID: <1223409364.17233.8.camel@localhost> (raw)
In-Reply-To: <48E95FEE.5050806@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1918 bytes --]
On E, 2008-10-06 at 03:46 +0300, Petteri Räty wrote:
> With USE="doc" the GNOME packages behave like what you expect but it's
> the USE="-doc" case that's in question here. With USE="-doc" you don't
> get any use flags installed normally and if it's in the tarball and is
> always installed then there is no doc in IUSE either. Global use flags
> should behave about the same for both on and off cases.
So you propose we would always install the documentation, but have a new
global USE flag (remember, we are talking about over a hundred of
packages here - everything that inherits gnome2.eclass) with a yet to be
determined name to control the re-generation?
However, with the advancements of the gtk-doc system, there _might_ not
be any more benefits in rebuilding the documentation, so I've had the
intention to check that out and perhaps propose removing the doc USE
flag completely and never regenerate it if it's true that it has no
point. But checking this has been quite a low priority, and given that
we need to get GNOME-2.24 out there for the users, it remains so during
this month, at least for me.
I would propose that we (the GNOME team) investigates the benefits (or
lack thereof these days) of the regeneration in the first part of
November, and if we don't, you get to remind us and we take care of it
as the hurry with a new major GNOME version, that users are awaiting
(including squashing all bugs needed before stabilization), will be over
then.
Taking the renaming of the USE flag approach as a start would also mean
touching many GNOME packages (build-depends on gtk-doc if eautoreconf is
involved), and I'd rather not risk that at the moment. It would also
heavily disrupts the moving of the new version ebuilds from overlay to
portage tree.
--
Mart Raudsepp
Gentoo Developer
Mail: leio@gentoo.org
Weblog: http://planet.gentoo.org/developers/leio
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
prev parent reply other threads:[~2008-10-07 19:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-05 13:05 [gentoo-dev] Changing doc use flag on gtk-doc packages to gtk-doc-rebuild or something else Petteri Räty
2008-10-05 13:29 ` Thomas Sachau
2008-10-05 16:27 ` Rémi Cardona
2008-10-05 18:34 ` Thomas Sachau
2008-10-05 19:54 ` Gilles Dartiguelongue
2008-10-05 23:24 ` Mart Raudsepp
2008-10-06 0:46 ` Petteri Räty
2008-10-07 19:56 ` Mart Raudsepp [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=1223409364.17233.8.camel@localhost \
--to=leio@gentoo.org \
--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