[Exherbo-dev] Tracking SCM revisions
ciaran.mccreesh at googlemail.com
Sun Feb 20 17:28:56 GMT 2011
As of now, we're tracking SCM revisions when installing packages that
make use of scm.exlib. This is step one of letting you not have to
rebuild scm packages that haven't actually changed if you don't want
to. You can see the results in 'cave show' output:
Summary Vim plugin: Exheres packages and exlibs
From repositories arbor
Installed time Sun Feb 20 17:18:37 GMT 2011
Installed using paludis-0.59.0-git-0.58.1-85-gc3d3be4
-trace Trace actions executed by the package
(very noisy, for debugging broken builds
SCM revision 13e8d5b0181ab2f08585697063bf0f4a2723e93b
This should also work for SCM pbins.
If you don't upgrade Paludis, you'll get some 'command not found'
messages for 'exsetscmrevision' when installing SCM packages. This
isn't fatal, so there's no fancy upgrade path you have to follow.
Only packages installed after you've upgraded Paludis will support
this. It's not retroactive.
If anything breaks it's dleverton's fault. If it all works it's due to
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 198 bytes
Desc: not available
More information about the Exherbo-dev