View previous topic :: View next topic |
Author |
Message |
Tony0945 Watchman
Joined: 25 Jul 2006 Posts: 5127 Location: Illinois, USA
|
Posted: Sat Nov 01, 2008 2:42 am Post subject: How to save work directories? [SOLVED] |
|
|
Sometimes, particularly when emerging an unstable package, I would like to examine the source code to find the source of the bug. My "work" directories seem to be erased after a successful emerge. How do I save them for debugging? Is there a global portage setting or an option to emerge?
Last edited by Tony0945 on Wed Dec 24, 2008 1:50 am; edited 1 time in total |
|
Back to top |
|
|
yabbadabbadont Advocate
Joined: 14 Mar 2003 Posts: 4791 Location: 2 exits past crazy
|
Posted: Sat Nov 01, 2008 2:55 am Post subject: |
|
|
You can use "ebuild package-ebuild-name unpack" to unpack and patch the sources to the /var/tmp/portage tree.
You may have to use the full path to the ebuild file, but I'm sure that you have to use the full ebuild file name including the version. |
|
Back to top |
|
|
Genone Retired Dev
Joined: 14 Mar 2003 Posts: 9527 Location: beyond the rim
|
Posted: Sat Nov 01, 2008 2:56 am Post subject: |
|
|
Code: | FEATURES="keepwork" |
Though be careful with enabling that permanently, it may cause weird side effects (it's only intended to be enabled temporary for debugging purposes). |
|
Back to top |
|
|
Tony0945 Watchman
Joined: 25 Jul 2006 Posts: 5127 Location: Illinois, USA
|
Posted: Sat Nov 01, 2008 9:29 pm Post subject: RESOLVED: How to save work directories? |
|
|
Two methods! Thanks for the prompt help. I'm a gentoo noob, but have embedded programming experience. Maybe I can help with the many ~amd64 packages once I have more experience. I hate pretending that this fine dual-core is an old athlon-xp. |
|
Back to top |
|
|
easy target Tux's lil' helper
Joined: 09 Jan 2008 Posts: 134
|
Posted: Sat Nov 01, 2008 11:09 pm Post subject: |
|
|
You may also try to build this package somewhere inside your home directory and test it as a regular user. This way you can check if a bug is gentoo specific (maybe because of a bug in an ebuild) or if it exists even when you build the package yourself. |
|
Back to top |
|
|
|