From: Troy Dack <troy@tkdack.com>
To: Jon Ellis <ashura666@mac.com>
Cc: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Fwd: cvs ebuilds
Date: Fri, 20 Dec 2002 15:59:03 +1100 [thread overview]
Message-ID: <3E02A397.7050402@tkdack.com> (raw)
In-Reply-To: <3487538.1040359160786.JavaMail.ashura666@mac.com>
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
next prev parent reply other threads:[~2002-12-20 5:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-20 4:39 [gentoo-dev] Fwd: cvs ebuilds Jon Ellis
2002-12-20 4:59 ` Troy Dack [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-12-20 5:14 Jon Ellis
2002-12-20 9:49 ` Mark Gordon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3E02A397.7050402@tkdack.com \
--to=troy@tkdack.com \
--cc=ashura666@mac.com \
--cc=gentoo-dev@gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox