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