As per policy: <antarus> "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." repo should be told to make make it a fatal error to try and commit a livecd ebuild to the tree. Chances are you could trigger the check simply on if an ebuild inherits the cvs/git/darcs eclasses or not.
I'll make make a livecd patch right away sir.
live(cvs|git|darcs|other).. :p
Created attachment 88373 [details, diff] Adds a VCS check for stable keywords
in -r3458
Thanks for taking care of this and supplying the patch. One small suggested change. -Ebuilds that inherit a "Live" eclasss (darcs,subversion,git,cvs,etc..) should -not be allowed to be marked stable +Ebuilds that inherit a "Live" eclass (darcs,subversion,git,cvs,etc..) are +not be allowed to be marked stable
released as a warning in 2.1 stable.