2015-03-28 14:43 GMT-06:00 James <wirel...@tampabay.rr.com>:
> likewise I've been hacking at ebuilds for apache (spark and mesos)
> The spark file are still under /var/tmp/portage/sys-cluster but the mesos
> files, compiled just yesterday are not under /var/tmp/portage. The
> same is true for ebuild in the portage tree. Some are there, some remain
> and others.... who knows.
>
This depends on wheter the ebuild was succesfully built, if so:
ebuild ${ebuild_path} clean
is called and all the files under /var/tmp/portage/cat/pkg are removed
When I'm trying to make an ebuild I only use the ebuild(5) tool, for
building, and call manually up to where I want to build(prepare,
configure, compile, etc...) and only when
ebuild ${ebuild_path} package
Has completed successfully, I use emerge so I don't get unwanted cleanups.
> So with this in mind, how do I "tag" certain ebuilds to at least save the
> configure.ac and Makefile.am files only for selected ebuild; either of which
> may be in /usr/portage or /usr/local/portage? (sorry for not being more
> clear). Is this just some inconsistency in how various ebuilds are
> constructed?
>
I don't see the utility of having these files apart form it's source
tree, if you modified them, then make patches, I usually unpack the
sources to a directory under $HOME, or clone the upstream repo, try to
get a working build as my user(I build experimental stuff with
--prefix="$HOME/opt/" so my system stays clean). Make a patch of my
changes if any, and then try to introduce the patch into an ebuild.
