Re: [gentoo-dev] Gentoo as a development platform

[Paul de Vrieze <pauldv@gentoo.org>]

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

On Sunday 17 April 2005 02:07, Daniel Drake wrote:
> 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.

My approach to this problem is most of the time to do the first steps on the 
cvs tree (make -f Makefile.cvs) to create the configure script. Then pack 
this up in a tarbal. Copy the old ebuild to my overlay, with a new name (or 
revision in the -r990 -r999 range). Change the source location in the new 
ebuild. Digest the stuff. And emerge it.

Paul

-- 
Paul de Vrieze
Gentoo Developer
Mail: pauldv@gentoo.org
Homepage: http://www.devrieze.net

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