On Wed, 2005-07-06 at 20:14 -0400, Aron Griffis wrote:
> Sven Wegener wrote: [Wed Jul 06 2005, 08:04:04PM EDT]
> > I'm writing this mail to bring you a thought we had over on freenode
> > in the #gentoo-portage channel. We would like to split up
> > src_compile. The new src_configure should just do the econf part and
> > src_compile should do the emake part. This represents the general
> > 3-step[1] installation in a much better way.
>
> This would be great in that it would be possible to do:
>
> ebuild blah.ebuild configure
>
> then change to the directory and work on it. But the other side of
> the coin is that you're talking about a LOT of ebuild changes, right?
Why would it require ebuild changes?
src_compile() currently does config + compile
src_configure() does configure, src_compile() does compile. If the
ebuild does both and configs in both then - duh - shoot the ebuild
maintainer!
All that needs to be added to the ebuild proggy is
if [[ $( type -t src_configure ) == "function" ]]; then
src_configure
elif [[ ${args} == "configure" ]]; then
ewarn "No configure function in ebuild!"
fi
src_compile
ebuilds could be changed over time - unless I'm missing something basic
here ..
--
gentoo-dev@gentoo.org mailing list
