public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
* [gentoo-dev] Fwd: cvs ebuilds
@ 2002-12-20  4:39 Jon Ellis
  2002-12-20  4:59 ` Troy Dack
  0 siblings, 1 reply; 4+ messages in thread
From: Jon Ellis @ 2002-12-20  4:39 UTC (permalink / raw
  To: gentoo-dev

[-- Attachment #1: Type: text/plain, Size: 868 bytes --]

Hi,

Any comments on this?

Thanks

j. 

From: Spider <spider@gentoo.org>
TO: Jon Ellis <ashura666@mac.com>
CC: 
Date: Fri December 20, 2002 12:48:34 PM JST
Subject: Re: [gentoo-user] cvs ebuilds

use -dev for this sort,  -user is the wrong place :)
//Spider

begin  quote
On Mon, 16 Dec 2002 09:39:37 +0900
Jon Ellis <ashura666@mac.com> wrote:

> Is there a 'policy' about cvs ebuilds? For example, i just created a 
> ebuild to build jack (jack audio connection kit) from cvs and updated 
> ardour to depend on it.
> 
> What troubles me is that i created a new sub-dir in my local portage
> to do this (media-sound/jack-cvs). The current jack ebuilds are in 
> media-sound/jack-audio-connection-kit. Is this the best way to do
> this? Wouldn't it be better to keep the cvs build in same directory?
> Is it possible to do that, the naming was beyond me...
> 
> j.
> 

[-- Attachment #2: Type: application/pgp-signature, Size: 190 bytes --]

[-- Attachment #3: Type: text/plain, Size: 37 bytes --]

--
gentoo-dev@gentoo.org mailing list

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [gentoo-dev] Fwd: cvs ebuilds
  2002-12-20  4:39 Jon Ellis
@ 2002-12-20  4:59 ` Troy Dack
  0 siblings, 0 replies; 4+ messages in thread
From: Troy Dack @ 2002-12-20  4:59 UTC (permalink / raw
  To: Jon Ellis; +Cc: gentoo-dev

Jon Ellis wrote:
> Hi,
> 
> Any comments on this?
> 
> Thanks
> 
> j. 
> 
> From: Spider <spider@gentoo.org>
> TO: Jon Ellis <ashura666@mac.com>
> CC: 
> Date: Fri December 20, 2002 12:48:34 PM JST
> Subject: Re: [gentoo-user] cvs ebuilds
> 
> use -dev for this sort,  -user is the wrong place :)
> //Spider
> 
> begin  quote
> On Mon, 16 Dec 2002 09:39:37 +0900
> Jon Ellis <ashura666@mac.com> wrote:
> 
> 
>>Is there a 'policy' about cvs ebuilds? For example, i just created a 
>>ebuild to build jack (jack audio connection kit) from cvs and updated 
>>ardour to depend on it.
>>
>>What troubles me is that i created a new sub-dir in my local portage
>>to do this (media-sound/jack-cvs). The current jack ebuilds are in 
>>media-sound/jack-audio-connection-kit. Is this the best way to do
>>this? Wouldn't it be better to keep the cvs build in same directory?
>>Is it possible to do that, the naming was beyond me...

 From http://www.gentoo.org/doc/en/policy.xml#doc_chap2 :

<quote>
"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.
</quote>

There is some more there that may be of interest to you.
-- 
	Troy Dack
	http://linux.tkdack.com		http://webportage.sf.net



--
gentoo-dev@gentoo.org mailing list


^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [gentoo-dev] Fwd: cvs ebuilds
@ 2002-12-20  5:14 Jon Ellis
  2002-12-20  9:49 ` Mark Gordon
  0 siblings, 1 reply; 4+ messages in thread
From: Jon Ellis @ 2002-12-20  5:14 UTC (permalink / raw
  To: Troy Dack; +Cc: gentoo-dev

On Friday, Dec 20, 2002, at 01:59PM, Troy Dack <troy@tkdack.com> wrote:
>
> From http://www.gentoo.org/doc/en/policy.xml#doc_chap2 :
>
><quote>
>"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.
></quote>
>
>There is some more there that may be of interest to you.

Thanks.

In this particular case There are no bundles available for ardour. There are also no bundles available for the version of jack upon which ardour depends. Reading the above link this sounds like a live cvs.eclass ebuild that will remain masked for it's lifetime. (The main developer of Ardour does not want people to create bundles as the current rate of development almost immediately invalidates them.)

The alternative to checking ebuilds into portage is to maintain a seperate website where the ebuilds are downloadable. This is far from ideal as there are many packages that depend on the current cvs version of jack.

If the person responsible for media-sound would like to contact me perhaps we can work out some way to make this work.

Cheers

j.

--
gentoo-dev@gentoo.org mailing list


^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [gentoo-dev] Fwd: cvs ebuilds
  2002-12-20  5:14 [gentoo-dev] Fwd: cvs ebuilds Jon Ellis
@ 2002-12-20  9:49 ` Mark Gordon
  0 siblings, 0 replies; 4+ messages in thread
From: Mark Gordon @ 2002-12-20  9:49 UTC (permalink / raw
  To: gentoo-dev

On Thu, 19 Dec 2002 21:14:48 -0800 (PST)
Jon Ellis <ashura666@mac.com> wrote:

> On Friday, Dec 20, 2002, at 01:59PM, Troy Dack <troy@tkdack.com>
> wrote:
> >
> > From http://www.gentoo.org/doc/en/policy.xml#doc_chap2 :
> >
> ><quote>
> >"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.
> ></quote>
> >
> >There is some more there that may be of interest to you.
> 
> Thanks.
> 
> In this particular case There are no bundles available for ardour.
> There are also no bundles available for the version of jack upon which
> ardour depends. Reading the above link this sounds like a live
> cvs.eclass ebuild that will remain masked for it's lifetime. (The main
> developer of Ardour does not want people to create bundles as the
> current rate of development almost immediately invalidates them.)
> 
> The alternative to checking ebuilds into portage is to maintain a
> seperate website where the ebuilds are downloadable. This is far from
> ideal as there are many packages that depend on the current cvs
> version of jack.
> 
> If the person responsible for media-sound would like to contact me
> perhaps we can work out some way to make this work.

One possibility would be to ask some nice person with plenty of unused
web space to host regular weekly tarballs pulled from CVS. Of course,
there would also be a lot of work producing ebuilds and checking them.
-- 
Mark Gordon
A friendly person with 20MB unused web space.

--
gentoo-dev@gentoo.org mailing list


^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2002-12-20  9:51 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2002-12-20  5:14 [gentoo-dev] Fwd: cvs ebuilds Jon Ellis
2002-12-20  9:49 ` Mark Gordon
  -- strict thread matches above, loose matches on Subject: below --
2002-12-20  4:39 Jon Ellis
2002-12-20  4:59 ` Troy Dack

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox