Slipping this in before 2.1 goes stable, it's a small check.
Basically if your ebuild inherits a VCS eclass ( currently darcs,
subversion, cvs ) AND your ebuild has stable keywords on any arches
repoman will report an error.
One thing to note here:
Are there any cases when one inherits a VCS eclass but the ebuild itself
is not a live checkout ebuild.
I don't see any, looking at the eclasses.
This repoman check attempts to enforce policy in the developer handbook[1].
""Live" cvs.eclass ebuilds are generally only intended for the
convenience of developers and should always be masked with a ~[arch]
keyword. It is impossible to guarantee the reliability of a "live"
cvs.eclass ebuild since the upstream cvs tree may change at any time,
which is why they should always be masked.
Whether a "live" CVS ebuild or a "snapshot" CVS ebuild, you the
developer are responsible for ensuring that the ebuild works correctly.
This is particularly difficult to do with "live" cvs ebuilds for obvious
reasons."
[1]http://www.gentoo.org/proj/en/devrel/handbook/handbook.xml?part=3&chap=1#doc_chap4
--
gentoo-dev@gentoo.org mailing list
