From: Donnie Berkholz <spyderous@gentoo.org>
To: Gentoo Developers <gentoo-dev@lists.gentoo.org>
Subject: [gentoo-dev] Annoying X.Org tarball naming (and how to deal with it)
Date: Wed, 21 Dec 2005 21:34:46 -0800 [thread overview]
Message-ID: <43AA3AF6.6000903@gentoo.org> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I'd appreciate some ideas better than what I've come up with so far to
deal with the very strange X.Org release naming.
When modular tarballs are part of a full X.Org release (7.0, 7.1, etc),
then they are named PN-PV-XORG_RELEASE.tar.(gz|bz2) and S matches. When
modular tarballs are independently released outside a full X.Org
release, they are named the standard way -- PN-PV.tar.(gz|bz2), same for S.
Dealing with this all in an automated fashion in x-modular.eclass is
somewhat difficult, and here's what I've come up with:
A variable (XORG_PV), set by the ebuild, to tell _which_ release it's
part of when it is part of a full release. If it's set, that means (1)
it is part of a full release and (2) indicates which release it's part of.
What does this mean for the future? All modular X ebuilds that are part
of a full release will require XORG_PV to be set. All modular X ebuilds
that aren't part of a full release will not require anything new. I'm
doing it this way because I expect there to be more packages that aren't
part of a full release than ones that are.
Please give me your input on this.
Thanks,
Donnie
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
iD8DBQFDqjr2XVaO67S1rtsRAhlPAKCMvjj82U6sNPpVYsUOnKOsRwAF4QCgibKM
Ccs1TnSQbXI66BVpf4P8Ed4=
=NFr1
-----END PGP SIGNATURE-----
--
gentoo-dev@gentoo.org mailing list
next reply other threads:[~2005-12-22 5:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-22 5:34 Donnie Berkholz [this message]
2005-12-22 15:17 ` [gentoo-dev] Annoying X.Org tarball naming (and how to deal with it) Ferris McCormick
2005-12-22 15:23 ` Donnie Berkholz
2005-12-23 3:57 ` Donnie Berkholz
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=43AA3AF6.6000903@gentoo.org \
--to=spyderous@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