1 |
On Thu, 19 Dec 2002 21:14:48 -0800 (PST) |
2 |
Jon Ellis <ashura666@×××.com> wrote: |
3 |
|
4 |
> On Friday, Dec 20, 2002, at 01:59PM, Troy Dack <troy@××××××.com> |
5 |
> wrote: |
6 |
> > |
7 |
> > From http://www.gentoo.org/doc/en/policy.xml#doc_chap2 : |
8 |
> > |
9 |
> ><quote> |
10 |
> >"live" cvs.eclass ebuilds are generally only intended for the |
11 |
> >convenience of developers and should always be masked with a ~[arch] |
12 |
> >keyword. It is impossible to guarantee the reliability of a "live" |
13 |
> >cvs.eclass ebuild since the upstream cvs tree may change at any time, |
14 |
> > which is why they should always be masked. |
15 |
> ></quote> |
16 |
> > |
17 |
> >There is some more there that may be of interest to you. |
18 |
> |
19 |
> Thanks. |
20 |
> |
21 |
> In this particular case There are no bundles available for ardour. |
22 |
> There are also no bundles available for the version of jack upon which |
23 |
> ardour depends. Reading the above link this sounds like a live |
24 |
> cvs.eclass ebuild that will remain masked for it's lifetime. (The main |
25 |
> developer of Ardour does not want people to create bundles as the |
26 |
> current rate of development almost immediately invalidates them.) |
27 |
> |
28 |
> The alternative to checking ebuilds into portage is to maintain a |
29 |
> seperate website where the ebuilds are downloadable. This is far from |
30 |
> ideal as there are many packages that depend on the current cvs |
31 |
> version of jack. |
32 |
> |
33 |
> If the person responsible for media-sound would like to contact me |
34 |
> perhaps we can work out some way to make this work. |
35 |
|
36 |
One possibility would be to ask some nice person with plenty of unused |
37 |
web space to host regular weekly tarballs pulled from CVS. Of course, |
38 |
there would also be a lot of work producing ebuilds and checking them. |
39 |
-- |
40 |
Mark Gordon |
41 |
A friendly person with 20MB unused web space. |
42 |
|
43 |
-- |
44 |
gentoo-dev@g.o mailing list |