On 05/06/2013 04:37 PM, Michael Hampicke wrote: > Am 07.05.2013 01:22, schrieb walt: >> On 05/05/2013 01:38 PM, Alan Mackenzie wrote: >> >>> There doesn't appear to be any action in emerge which unpacks the build >>> files (or even the entire source) of a package for perusal. This is a >>> shame. >> >> You should become familiar with the 'ebuild' command, which I use very >> often when trying to debug a package, e.g. >> >> #ebuild /usr/portage/app-office/libreoffice/libreoffice-3.6.6.2.ebuild unpack >> >> To completely build and install a package you need to follow that command >> with the 'configure', 'compile', 'install', and 'qmerge' steps (man ebuild). >> > > If you are lazy like me,
No way! I'm lazier than you :p > and don't want to execute all steps manually, > just use ebuild <package.ebuild> merge :) The reason it's nice to know the individual steps is that there can be bugs at any of those steps along the way (usually during the configure or compile phases) and if the bug is simple enough you can edit the broken files and then restart the merge. Often someone will add a patch to an existing bug report, which you can apply to a failed emerge and then restart the compile phase without starting from scratch. I'm guessing you know all of this already, but Alan and others may not know. The more debuggers, the merrier :)
