From: Mart Raudsepp <leio@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [RFC] New global USE flag: gtk-doc
Date: Thu, 30 Aug 2018 21:38:48 +0300 [thread overview]
Message-ID: <1535654328.2247.7.camel@gentoo.org> (raw)
In-Reply-To: <1535141206.6451.19.camel@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1069 bytes --]
Ühel kenal päeval, R, 24.08.2018 kell 23:06, kirjutas Mart Raudsepp:
> Longer version idea:
> Build and install gtk-doc based developer documentation for dev-
> util/devhelp, IDE and offline use
This has been pushed now with initial consumers (fresh meson based
packages or converts from autotools).
I have a candidate list of packages that could use a IUSE flag usage
change accordingly. It's a short list because I didn't consider
autotools packages, as for them it often means to rebuild it for
questionable benefits, thus I don't actually want those cases to add
unnecessary rebuild time cost with a global USE=gtk-doc - they are
already there without current USE=doc and accessible in devhelp and
some IDEs. This means autotools builds that don't use a properly disted
tarball won't get a bug filed from me right now (but why are they using
a bad tarball?).
I'll try to get those from my candidate list checked through and
converted to bug reports soon for applicable ones. If more than lets
say 3, then probably a tracker bug too.
Mart
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 981 bytes --]
prev parent reply other threads:[~2018-08-30 18:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-24 20:06 [gentoo-dev] [RFC] New global USE flag: gtk-doc Mart Raudsepp
2018-08-25 23:08 ` David Haller
2018-08-26 9:15 ` Mart Raudsepp
2018-08-26 2:19 ` Andrew Savchenko
2018-08-26 9:08 ` Mart Raudsepp
2018-08-30 18:38 ` 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=1535654328.2247.7.camel@gentoo.org \
--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