-----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
