| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
Daniel Drake wrote: |
| 5 |
> Gentoo is fairly well oriented for this kind of environment, but it's not |
| 6 |
> brilliant. As an example, foo-3.2.1 (the latest version) is installed on my |
| 7 |
> system, but more recently, they fixed a critical bug in the upstream CVS tree |
| 8 |
> which I'd like to test the fix for. It's not dead simple for me to do this - I |
| 9 |
> want to use the CVS sources with the ebuild already in portage. I have to use |
| 10 |
> "ebuild foo-3.2.1.ebuild unpack" to extract the sources, then manually replace |
| 11 |
> them with my CVS checkout. Or checkout CVS, make a new tarball, call it |
| 12 |
> foo-3.2.1.tar.bz2, redigest and remerge the ebuild. Or I could create a |
| 13 |
> foo-cvs ebuild and go to the trouble of making it mirror the contents of |
| 14 |
> foo-3.2.1.ebuild exactly. |
| 15 |
|
| 16 |
I generally just bump the version of a current ebuild to reflect a dated |
| 17 |
tarball that's a CVS snapshot, e.g. foo-3.2.1_p20050416 or foo-20050416. |
| 18 |
|
| 19 |
Then do FEATURES=digest emerge foo, and it'll create the digest for ya |
| 20 |
and update. |
| 21 |
|
| 22 |
Carefully combined with FEATURES like keeptemp and keepwork, this could |
| 23 |
do nearly what you suggest. |
| 24 |
|
| 25 |
Using the same exact ebuild for multiple versions seems like a recipe |
| 26 |
for disaster. |
| 27 |
-----BEGIN PGP SIGNATURE----- |
| 28 |
Version: GnuPG v1.4.1 (GNU/Linux) |
| 29 |
|
| 30 |
iD8DBQFCYb4UXVaO67S1rtsRAnQWAJoCHQXAQ4rEhAAL/UvJhwVQEJp02gCfTUbE |
| 31 |
N4D9t1unZuXNkPfuLoa/jNI= |
| 32 |
=5tYo |
| 33 |
-----END PGP SIGNATURE----- |
| 34 |
-- |
| 35 |
gentoo-dev@g.o mailing list |
Archives