On Thursday 03 April 2003 23:39, Vano D wrote: > Probably we could add a feature to emerge so one would "emerge > --custom some_source" and Portage would untar into the work dir the > file /usr/portate/distfiles/some_source-2.9.tar.gz (or other > extensions etc..) and would carry out a simple skel.ebuild (or we > could have 2 or 3 other variations if the first one or two fail to > compile). It would then enter into the Portage database as > "custom.some_source-2.9" or with some other prefix so Portage knows > it is a "special ebuild" (as in there is no ebuild.) > > It doesn't look too hard to implement such a feature. What do you > people think?
One obvious pitfall is dependencies. Tool to make ebuilds easily can be found from portage, but those could be improved a lot. -- [EMAIL PROTECTED] mailing list
