1 |
Jon Ellis wrote: |
2 |
> Hi, |
3 |
> |
4 |
> Any comments on this? |
5 |
> |
6 |
> Thanks |
7 |
> |
8 |
> j. |
9 |
> |
10 |
> From: Spider <spider@g.o> |
11 |
> TO: Jon Ellis <ashura666@×××.com> |
12 |
> CC: |
13 |
> Date: Fri December 20, 2002 12:48:34 PM JST |
14 |
> Subject: Re: [gentoo-user] cvs ebuilds |
15 |
> |
16 |
> use -dev for this sort, -user is the wrong place :) |
17 |
> //Spider |
18 |
> |
19 |
> begin quote |
20 |
> On Mon, 16 Dec 2002 09:39:37 +0900 |
21 |
> Jon Ellis <ashura666@×××.com> wrote: |
22 |
> |
23 |
> |
24 |
>>Is there a 'policy' about cvs ebuilds? For example, i just created a |
25 |
>>ebuild to build jack (jack audio connection kit) from cvs and updated |
26 |
>>ardour to depend on it. |
27 |
>> |
28 |
>>What troubles me is that i created a new sub-dir in my local portage |
29 |
>>to do this (media-sound/jack-cvs). The current jack ebuilds are in |
30 |
>>media-sound/jack-audio-connection-kit. Is this the best way to do |
31 |
>>this? Wouldn't it be better to keep the cvs build in same directory? |
32 |
>>Is it possible to do that, the naming was beyond me... |
33 |
|
34 |
From http://www.gentoo.org/doc/en/policy.xml#doc_chap2 : |
35 |
|
36 |
<quote> |
37 |
"live" cvs.eclass ebuilds are generally only intended for the |
38 |
convenience of developers and should always be masked with a ~[arch] |
39 |
keyword. It is impossible to guarantee the reliability of a "live" |
40 |
cvs.eclass ebuild since the upstream cvs tree may change at any time, |
41 |
which is why they should always be masked. |
42 |
</quote> |
43 |
|
44 |
There is some more there that may be of interest to you. |
45 |
-- |
46 |
Troy Dack |
47 |
http://linux.tkdack.com http://webportage.sf.net |
48 |
|
49 |
|
50 |
|
51 |
-- |
52 |
gentoo-dev@g.o mailing list |