| 1 |
* Michael Orlitzky <mjo@g.o> [150328 12:11]: |
| 2 |
> On 03/28/2015 10:36 AM, James wrote: |
| 3 |
> > James <wireless <at> tampabay.rr.com> writes: |
| 4 |
> > |
| 5 |
> > |
| 6 |
> >> Often, I need to inspect and ponder these files: configure.ac and Makefile |
| 7 |
> >> .am for a given ebuild. Is there an easy way to look at them with |
| 8 |
> >> compiling the ebuild ? |
| 9 |
> > |
| 10 |
> > oops, |
| 11 |
> > |
| 12 |
> > Should be : Often, I need to inspect and ponder these files: configure.ac |
| 13 |
> > and Makefile.am for a given ebuild. Is there an easy way to look at them |
| 14 |
> > *without* compiling the ebuild ? |
| 15 |
> > |
| 16 |
> |
| 17 |
> Those files are part of the upstream tarball. The easiest way to fetch |
| 18 |
> the sources without compiling them is with `emerge -f`. Then you can |
| 19 |
> copy the tarball out of $DISTDIR and unpack it somewhere. |
| 20 |
> |
| 21 |
> Some ebuilds may patch configure.ac or Makefile.am -- in that case it's |
| 22 |
> a little harder. I'm sure there's an elegant way to do it, but what I |
| 23 |
> usually do is begin to emerge the package and Ctrl-C it when it starts |
| 24 |
> compiling. Then you can find the sources under /var/tmp/portage. |
| 25 |
> |
| 26 |
|
| 27 |
Wouldn't 'ebuild <ebuild_file_name> prepare' do what you want without |
| 28 |
trying to time a Ctrl-C? |
Archives