Bug 135531

Summary:	Request for repoman to disallow stable markings in live* ebuilds
Product:	Gentoo Linux	Reporter:	solar (RETIRED) <solar>
Component:	New packages	Assignee:	Alec Warner (RETIRED) <antarus>
Status:	RESOLVED FIXED
Severity:	normal	Keywords:	InVCS
Priority:	High
Version:	2006.0
Hardware:	All
OS:	All
Whiteboard:
Package list:		Runtime testing required:	---
Attachments:	Adds a VCS check for stable keywords

Description solar (RETIRED) gentoo-dev

2006-06-04 09:15:05 UTC

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.

Comment 1 Alec Warner (RETIRED) archtester

2006-06-04 09:17:14 UTC

I'll make make a livecd patch right away sir.

Comment 2 solar (RETIRED) gentoo-dev

2006-06-04 09:18:10 UTC

live(cvs|git|darcs|other).. :p

Comment 3 Alec Warner (RETIRED) archtester

2006-06-04 12:50:59 UTC

Created attachment 88373 [details, diff]
Adds a VCS check for stable keywords

Comment 4 Alec Warner (RETIRED) archtester

2006-06-04 12:51:32 UTC

in -r3458

Comment 5 solar (RETIRED) gentoo-dev

2006-06-04 14:39:06 UTC

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

Comment 6 Alec Warner (RETIRED) archtester

2006-06-14 17:20:16 UTC

released as a warning in 2.1 stable.