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
