the source tarball is kept in /usr/portage/distfiles (in its tarred
release format). You can study the "raw" (as in unpatched ) source there
by untarring the source tarball.
as others have said, if you want to study the source with whatever
patches the ebuild has applied, use "FEATURES=keepwork"
cfk wrote:
>Pardon the slightly naive question.
>
>I would like to study the c and cpp source on the packages I am emerging. I
>*think* they are removed after compilation. I say I *think* as I was looking
>in /var/tmp/portage and /usr/portage and didnt find them.
>
>How do I go about keeping the
On Fri, 2005-05-20 at 17:38 -0700, cfk wrote:
> I would like to study the c and cpp source on the packages I am emerging. I
> *think* they are removed after compilation. I say I *think* as I was looking
> in /var/tmp/portage and /usr/portage and didnt find them.
>
> How do I go about keeping the
--- cfk <[EMAIL PROTECTED]> wrote:
> Pardon the slightly naive question.
>
> I would like to study the c and cpp source on the
> packages I am emerging. I
> *think* they are removed after compilation. I say I
> *think* as I was looking
> in /var/tmp/portage and /usr/portage and didnt find
> the
Check out the features in /etc/make.conf. You can tell emerge to leave
the source behind.
On Fri, 20 May 2005, cfk wrote:
Pardon the slightly naive question.
I would like to study the c and cpp source on the packages I am emerging. I
*think* they are removed after compilation. I say I *think* as
Pardon the slightly naive question.
I would like to study the c and cpp source on the packages I am emerging. I
*think* they are removed after compilation. I say I *think* as I was looking
in /var/tmp/portage and /usr/portage and didnt find them.
How do I go about keeping the source for later r
6 matches
Mail list logo
