> > I use stow, never heard of epkg before, can you elucidate on the > > differences between them, or perchance why epkg is a better choice? > > Why just not write an ebuild. Often even the skel ebuild just works with your > package, and you just need to add the url. (/usr/portage/skel.ebuild) > > It is really easy to write ebuilds, and if you made some mistake you can often > just go on where you left after correcting the problem.
I have been wondering a lot lately whether it is possible to have a mechanism in Portage to install software which just requires a configure, make, make install. We know that usually using the skel.ebuild is enough. 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? -- Vano D <[EMAIL PROTECTED]> -- [EMAIL PROTECTED] mailing list
