From: Daniel Drake <dsd@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Gentoo as a development platform
Date: Sun, 17 Apr 2005 01:07:50 +0100 [thread overview]
Message-ID: <4261A8D6.4070308@gentoo.org> (raw)
In-Reply-To: <4261A320.4090302@pnpitalia.it>
Francesco Riosa wrote:
> Why do you semply add a "cat-ego/pack-cvs/pack-cvs.ebuild" near
> "cat-ego/pack/pack.ebuild" without get bothered with virtual and similar
> you can simply unmerge and remerge the brother package.
> There are many examples of merging from cvs in portage tree.
Portage doesn't contain many cvs ebuilds. Writing one might not be that much
hassle, but why should I have to? We already have functional ebuilds to build
that particular package, and I have some slightly newer source code (e.g. in
my homedir) that I want it to build instead.
If I did write a cvs ebuild, it would check out the sources *again* from CVS,
into /usr/portage/distfiles (I guess...). This is redundant and will take
quite a bit of time for larger packages. While this not that much of a
problem, one of my motives behind this is that I want to improve productivity.
Writing an ebuild *again* which checks out the sources *again* doesn't really
go in this direction.
Daniel
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2005-04-17 0:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-16 23:36 [gentoo-dev] Gentoo as a development platform Daniel Drake
2005-04-16 23:43 ` Francesco Riosa
2005-04-17 0:07 ` Daniel Drake [this message]
2005-04-17 0:13 ` Robert Paskowitz
2005-04-17 1:03 ` Daniel Drake
2005-04-17 16:24 ` Malte S. Stretz
2005-04-19 19:35 ` Paul de Vrieze
2005-04-16 23:43 ` Brian Harring
2005-04-17 0:03 ` Daniel Drake
2005-04-17 1:39 ` Donnie Berkholz
2005-04-17 2:26 ` Brian Harring
2005-04-17 0:48 ` Jason Cooper
2005-04-17 1:14 ` Brian Harring
2005-04-17 1:38 ` Donnie Berkholz
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=4261A8D6.4070308@gentoo.org \
--to=dsd@gentoo.org \
--cc=gentoo-dev@lists.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