From: Mike Frysinger <vapier@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] sys-devel/gettext and implicit vcs packages (cvs/git)
Date: Wed, 4 Aug 2010 15:14:47 -0400 [thread overview]
Message-ID: <201008041514.48361.vapier@gentoo.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1343 bytes --]
the gettext package and its implicit vcs has been a problem for us for time
immemorial (one of the first documented instances is Bug 55607 dated Jun
2004). at the time, we really had no way of handling this cleanly. but with
USE deps now, i think we address this somewhat sanely.
background: the gettext package supports older versions of itself while
minimizing disk space by storing the deployable files in a vcs archive. this
is only used at runtime if you run `autopoint`, and that is only used during
development where the bundled gettext files in a package need to be recreated.
in the past, it only used cvs, but now it supports both cvs and git (which are
detected when gettext is emerged). in the past, we just forced the smallish
random packages that actually ran autotools to depend on cvs themselves.
what i'm proposing now is that we add a local USE flag (Nick proposed
"autopoint") to sys-devel/gettext. something like:
RDEPEND="autopoint? (
git? ( dev-vcs/git )
!git? ( cvs? ( dev-vcs/cvs ) )
!cvs? ( dev-vcs/git )
)"
idea is that we want to prefer git over cvs. now other packages can DEPEND on
sys-devel/gettext[autopoint]. perhaps even extend autotools.eclass with a
variable to indicate people are going to be using eautopoint ...
any counter proposals/etc... ?
-mike
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next reply other threads:[~2010-08-04 19:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-04 19:14 Mike Frysinger [this message]
[not found] <fdSrL-4Kk-9@gated-at.bofh.it>
2010-08-05 7:17 ` [gentoo-dev] sys-devel/gettext and implicit vcs packages (cvs/git) Vaeth
2010-08-05 16:38 ` Mike Frysinger
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=201008041514.48361.vapier@gentoo.org \
--to=vapier@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