| 1 |
Michael Orlitzky wrote: |
| 2 |
> On 03/28/2015 01:40 PM, Todd Goodman wrote: |
| 3 |
> >> |
| 4 |
> >> Some ebuilds may patch configure.ac or Makefile.am -- in that case it's |
| 5 |
> >> a little harder. I'm sure there's an elegant way to do it, but what I |
| 6 |
> >> usually do is begin to emerge the package and Ctrl-C it when it starts |
| 7 |
> >> compiling. Then you can find the sources under /var/tmp/portage. |
| 8 |
> >> |
| 9 |
> > |
| 10 |
> > Wouldn't 'ebuild <ebuild_file_name> prepare' do what you want without |
| 11 |
> > trying to time a Ctrl-C? |
| 12 |
> > |
| 13 |
> |
| 14 |
> Yeah, but I have to be in the directory where the ebuild lives for that |
| 15 |
> to work. `emerge foo` works anywhere. It's also more flexible -- if I |
| 16 |
> want the *unpatched* files, I just Ctrl-C earlier =) |
| 17 |
|
| 18 |
The ebuild-command works from every directory (at least for me ;)), you don't need to be inside |
| 19 |
the directory where the ebuild lives. |
| 20 |
And to get the unpatched src tree simply use "ebuild <EBUILD> unpack". After that you |
| 21 |
can run "ebuild <EBUILD> prepare" to prepare (e.g. patch) the sources. That's way easier to get |
| 22 |
a well defined result than hitting C-c :) |
Archives