[gentoo-user] Re: configure.ac and Makefile.am easy_view ?

[James]

Michael Orlitzky <mjo <at> gentoo.org> writes:


> Those files are part of the upstream tarball. The easiest way to fetch
> the sources without compiling them is with `emerge -f`. Then you can
> copy the tarball out of $DISTDIR and unpack it somewhere.

> Some ebuilds may patch configure.ac or Makefile.am -- in that case it's
> a little harder. I'm sure there's an elegant way to do it, but what I
> usually do is begin to emerge the package and Ctrl-C it when it starts
> compiling. Then you can find the sources under /var/tmp/portage.

Hmm... That's kinda what I've been doing. I want a way to save those
files, once I tag a given ebuild for this sort of curious  and closer
examination. GLEP_64 would go a long way to automating this, with
a DAG. I just wanted to make sure there was not an existing or easier
way to do this, that I had not considered.


Is there a way to includes those files for archiving so something like
elogviewer could make them available systematically? Do you think the
maintainer of elogviewer is open to that sort of request, formally (BGO) or
informally (personal email?). Another more suited tool for extending the
existing functionality to view key files of an ebuild?

Other ideas?


James