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