Michael Orlitzky wrote: > On 03/28/2015 01:40 PM, Todd Goodman wrote: > >> > >> 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. > >> > > > > Wouldn't 'ebuild <ebuild_file_name> prepare' do what you want without > > trying to time a Ctrl-C? > > > > Yeah, but I have to be in the directory where the ebuild lives for that > to work. `emerge foo` works anywhere. It's also more flexible -- if I > want the *unpatched* files, I just Ctrl-C earlier =)
The ebuild-command works from every directory (at least for me ;)), you don't need to be inside the directory where the ebuild lives. And to get the unpatched src tree simply use "ebuild <EBUILD> unpack". After that you can run "ebuild <EBUILD> prepare" to prepare (e.g. patch) the sources. That's way easier to get a well defined result than hitting C-c :)
