1 |
On Wed, 2005-12-21 at 21:34 -0800, Donnie Berkholz wrote: |
2 |
> -----BEGIN PGP SIGNED MESSAGE----- |
3 |
> Hash: SHA1 |
4 |
> |
5 |
> I'd appreciate some ideas better than what I've come up with so far to |
6 |
> deal with the very strange X.Org release naming. |
7 |
> |
8 |
> When modular tarballs are part of a full X.Org release (7.0, 7.1, etc), |
9 |
> then they are named PN-PV-XORG_RELEASE.tar.(gz|bz2) and S matches. When |
10 |
> modular tarballs are independently released outside a full X.Org |
11 |
> release, they are named the standard way -- PN-PV.tar.(gz|bz2), same for S. |
12 |
> |
13 |
> Dealing with this all in an automated fashion in x-modular.eclass is |
14 |
> somewhat difficult, and here's what I've come up with: |
15 |
> |
16 |
> A variable (XORG_PV), set by the ebuild, to tell _which_ release it's |
17 |
> part of when it is part of a full release. If it's set, that means (1) |
18 |
> it is part of a full release and (2) indicates which release it's part of. |
19 |
> |
20 |
> What does this mean for the future? All modular X ebuilds that are part |
21 |
> of a full release will require XORG_PV to be set. All modular X ebuilds |
22 |
> that aren't part of a full release will not require anything new. I'm |
23 |
> doing it this way because I expect there to be more packages that aren't |
24 |
> part of a full release than ones that are. |
25 |
> |
26 |
> Please give me your input on this. |
27 |
|
28 |
Seems fine to me. I hope you are right in your assumption about |
29 |
packages in full releases. |
30 |
|
31 |
> |
32 |
> Thanks, |
33 |
> Donnie |
34 |
> -----BEGIN PGP SIGNATURE----- |
35 |
> Version: GnuPG v1.4.2 (GNU/Linux) |
36 |
> |
37 |
> iD8DBQFDqjr2XVaO67S1rtsRAhlPAKCMvjj82U6sNPpVYsUOnKOsRwAF4QCgibKM |
38 |
> Ccs1TnSQbXI66BVpf4P8Ed4= |
39 |
> =NFr1 |
40 |
> -----END PGP SIGNATURE----- |
41 |
-- |
42 |
Ferris McCormick (P44646, MI) <fmccor@g.o> |
43 |
Developer, Gentoo Linux (Sparc, Devrel) |