Attachment #368100 for bug #421993

View | Details | Raw Unified | Return to bug 421993 | Differences between
Collapse All | Expand All





<p>
Note that CVS ebuilds should <b>not</b> generally be added to the tree
for the following reasons:
</p>

<ul>

<title>Using CVS Sources</title>
<body>

<note>
CVS ebuilds must be either with empty <c>KEYWORDS</c> or
package.masked (but <e>not</e> both). Empty <c>KEYWORDS</c> are
strongly preferred. This applies to "live" ebuilds (<c>-9999</c>) and
to ebuilds that extract a static revision but still use CVS for
fetching.
</note>

<p>
To use a CVS source, <c>cvs.eclass</c> must be inherited, and then a
number of variables must be set. The following variables are often





<p>
Note that Subversion ebuilds should <b>not</b> generally be added to
the tree for much the same reasons that live CVS ebuilds should not (see
that live CVS ebuilds should not (see
<uri link="::ebuild-writing/functions/src_unpack/cvs-sources#Disadvantages of CVS Sources"/>).
Indeed, there should be even less impetus to add a live Subversion ebuild than a live CVS ebuild, as
Subversion checkouts are roughly a factor of five larger than an

<title>Using Subversion Sources</title>
<body>

<note>
Subversion ebuilds must be either with empty <c>KEYWORDS</c> or
package.masked (but <e>not</e> both). Empty <c>KEYWORDS</c> are
strongly preferred. This applies to "live" ebuilds (<c>-9999</c>) and
to ebuilds that extract a static revision but still use Subversion for
fetching.
</note>

<p>
To use a Subversion source, <c>subversion.eclass</c> must be
inherited, and then at least <c>ESVN_REPO_URI</c> must be set. The
- 

Return to bug 421993

Lines 17-23 need to test unreleased snapshots on a regular basis. Link Here

(-)a/ebuild-writing/functions/src_unpack/cvs-sources/text.xml (-1 / +9 lines)
17		17
18	<p>	18	<p>
19	Note that CVS ebuilds should <b>not</b> generally be added to the tree	19	Note that CVS ebuilds should <b>not</b> generally be added to the tree
20	(except with <c>KEYWORDS=""</c>) for the following reasons:	20	for the following reasons:
21	</p>	21	</p>
22		22
23	<ul>	23	<ul>
Lines 76-81 date or revision are even worse candidates for tree inclusion: Link Here
76	<title>Using CVS Sources</title>	76	<title>Using CVS Sources</title>
77	<body>	77	<body>
78		78
		79	<note>
		80	CVS ebuilds must be either with empty <c>KEYWORDS</c> or
		81	package.masked (but <e>not</e> both). Empty <c>KEYWORDS</c> are
		82	strongly preferred. This applies to "live" ebuilds (<c>-9999</c>) and
		83	to ebuilds that extract a static revision but still use CVS for
		84	fetching.
		85	</note>
		86
79	<p>	87	<p>
80	To use a CVS source, <c>cvs.eclass</c> must be inherited, and then a	88	To use a CVS source, <c>cvs.eclass</c> must be inherited, and then a
81	number of variables must be set. The following variables are often	89	number of variables must be set. The following variables are often

Lines 19-26 ection. Link Here

(-)a/ebuild-writing/functions/src_unpack/svn-sources/text.xml (-3 / +9 lines)
19		19
20	<p>	20	<p>
21	Note that Subversion ebuilds should <b>not</b> generally be added to	21	Note that Subversion ebuilds should <b>not</b> generally be added to
22	the tree (unless introduced with <c>KEYWORDS=""</c>) for much the same reasons	22	the tree for much the same reasons that live CVS ebuilds should not (see
23	that live CVS ebuilds should not (see
24	<uri link="::ebuild-writing/functions/src_unpack/cvs-sources#Disadvantages of CVS Sources"/>).	23	<uri link="::ebuild-writing/functions/src_unpack/cvs-sources#Disadvantages of CVS Sources"/>).
25	Indeed, there should be even less impetus to add a live Subversion ebuild than a live CVS ebuild, as	24	Indeed, there should be even less impetus to add a live Subversion ebuild than a live CVS ebuild, as
26	Subversion checkouts are roughly a factor of five larger than an	25	Subversion checkouts are roughly a factor of five larger than an
Lines 42-47 $ svn export svn://svn.berlios.de/svnroot/repos/gentoo-syntax -r HEAD gentoo-syn Link Here
42	<title>Using Subversion Sources</title>	41	<title>Using Subversion Sources</title>
43	<body>	42	<body>
44		43
		44	<note>
		45	Subversion ebuilds must be either with empty <c>KEYWORDS</c> or
		46	package.masked (but <e>not</e> both). Empty <c>KEYWORDS</c> are
		47	strongly preferred. This applies to "live" ebuilds (<c>-9999</c>) and
		48	to ebuilds that extract a static revision but still use Subversion for
		49	fetching.
		50	</note>
		51
45	<p>	52	<p>
46	To use a Subversion source, <c>subversion.eclass</c> must be	53	To use a Subversion source, <c>subversion.eclass</c> must be
47	inherited, and then at least <c>ESVN_REPO_URI</c> must be set. The	54	inherited, and then at least <c>ESVN_REPO_URI</c> must be set. The
48	-