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:
app-vim/exheres-syntax-scm:0::installed
Homepage http://www.exherbo.org/
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
Licences vim
Options
Build Options
-trace Trace actions executed by the package
(very noisy, for debugging broken builds
only)
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
my brilliance.
--
Ciaran McCreesh
signature.asc
Description: PGP signature
_______________________________________________ Exherbo-dev mailing list [email protected] http://lists.exherbo.org/mailman/listinfo/exherbo-dev
