| View previous topic :: View next topic |
| Author |
Message |
sono
n00b
Joined: 02 Jul 2004
Posts: 15
|
 Posted: Fri Jul 02, 2004 4:44 pm Post subject: How to fiddle with package contens? |
 |
|
I want to trace a problem and would like to *at least* browse the source of the ebuild package in question before compiling it.
What would be the correct procedure?
I tried ebuild unpack but it is stuck here:
| Code: |
orion var # ebuild db/pkg/media-sound/alsa-driver-1.0.5a/alsa-driver-1.0.5a.ebuild unpack
>>> md5 src_uri ;-) alsa-driver-1.0.5a.tar.bz2
>>> Checking alsa-driver-1.0.5a.tar.bz2's mtime...
>>> Not marked as unpacked; recreating WORKDIR...
>>> Unpacking source...
>>> Unpacking alsa-driver-1.0.5a.tar.bz2 to /var/tmp/portage/alsa-driver-1.0.5a/work
* Cannot find $EPATCH_SOURCE! Value for $EPATCH_SOURCE is:
*
* /var/db/pkg/media-sound/alsa-driver-1.0.5a/files/alsa-driver-1.0.5-devfix.patch
!!! ERROR: media-sound/alsa-driver-1.0.5a failed.
!!! Function epatch, Line 182, Exitcode 0
!!! Cannot find $EPATCH_SOURCE!
|
|
|
| Back to top |
|
 |
steel300
Veteran
Joined: 10 Jul 2003
Posts: 1155
|
| Posted: Fri Jul 02, 2004 6:02 pm Post subject: |
|
|
you're doing it right, just using the wrong ebuild. The one you want to use is in /usr/portage/media-sound/alsa-driver. The ebuild it self is copied over to /var after the merge so you still have it as a reference.
_________________
Rationality is the recognition of the fact that nothing can alter the truth and nothing can take precedence over that act of perceiving it. |
|
| Back to top |
|
|
|
Other Things Gentoo
