-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I mainly lurk on this list..."hi all" ... waiting for that wonderful
day when framebuffer at full res works on my sad little intel 855gme
chipset laptop...anways:
On 2005-10-13 08:55:14 -0400 Unger Richard <[EMAIL PROTECTED]>
wrote:
Might I suggest the following?
-> For actual DFB releases, a ebuild like DirectFB-0.9.22.ebuild is
ideal.
-> For CVS releases, DirectFB-0.9.23 is not ideal, unless you go for
a
specific CVS Tag, since the version will not 'stick'. Ie if I install
the
ebuild today and again in 1 Week I will get different builds since
the
version in CVS has changed.
Other projects (for example enlightenment r17) get around this by
creating an
ebuild like:
DirectFB-9999.ebuild
The '9999' is a dummy version number and stands for 'CVS Head' - ie
the most
recent version possible. The '9999' ebuilds are typically marked ~x86
so if
you want a clean system just use the x86 builds, to risk CVS, use
ACCEPT_KEYWORDS="~x86"
If you have live cvs pulls:
- - use cvs.eclass
- - KEYWORDS="-*" (Don't *ever* mark a live cvs pull as testing or
stable. Ever.)
If you create a snapshot:
- - download, test, tar it up, post it
- - KEYWORDS="~arch" (and ~arch is best case, unless circumstances are
unusual)
Real releases:
- - the normal Gentoo ebuild dance; read the docs on this.
For a while, I maintained some ebuilds that pulled cvs sources with a
date spec; for you, this could look like
"directfb-0.9.23_pre20051013", if you pull the sources with a date
spec corresponding to 10/13/2005 12:00 AM, for e.g.
Sorry for all the noise, non-gentoo peoples,
__Armando Di Cianno
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1-ecc0.1.6 (GNU/Linux)
Comment: Using the GPG bundle for GNUMail
iD8DBQFDTsS2wgiTPLI9xhcRAipnAJwLKYnV1IJfASV8KXslSx25jEGoVwCcCxCk
C2DtuH/MG2xJR/Rv1fg6FMQ=
=qv/+
-----END PGP SIGNATURE-----
_______________________________________________
directfb-dev mailing list
[email protected]
http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-dev
