[gentoo-dev] How to test ebuild install without recompiling?

[gentoo-dev] How to test ebuild install without recompiling?

[Eric F Sorton]

Hi All,

I am in the process of creating an ebuild for "qcad".

The "build" step was created in short order.  The "install" step is,
however, giving me problems.  Currently, my biggest holdup is the cycle
time to test changes to my ebuild.  Each time I change my ebuild, when I
issue the "ebuild qcad-<vers>.ebuild install", I get a message stating
that the ebuild changed.  The working directory is erased.  As a
consequence of this, I have to watch my application be rebuilt (which
takes a few minutes).  

So, is there a way, when testing an ebuild, to force ebuild, the
application, NOT to rebuild the entire application.  I looked through
the manpage and the portage HOWTO, but I didn't see anything obvious.

Thanks for the assistance,

-- 
Eric F. Sorton <erics at cfl dot rr dot com>

Re: [gentoo-dev] How to test ebuild install without recompiling?

[Jared H. Hudson]

I believe you can edit your /etc/make.conf and add the word, noauto
to the FEATURES= line. I would add sandbox as well, since that's in the 
default FEATURES line in /etc/make.globals and will be overwritten.
So, you'll have something like:

FEATURES="sandbox noauto"

In case you're curious, the reason why it's re-compiling is that
whenever you run ebuild package install, it goes through all the steps 
leading up to install (unless the noauto keyword is in there).

In this case since you've modified the ebuild its mtime is greater than 
the uncompiled source, so when it does the unpack step it re-unpacks it 
and therefore has to re-compile it.

-Jared H.

On Fri, 12 Apr 2002, Eric F Sorton wrote:

> Hi All,
> 
> I am in the process of creating an ebuild for "qcad".
> 
> The "build" step was created in short order.  The "install" step is,
> however, giving me problems.  Currently, my biggest holdup is the cycle
> time to test changes to my ebuild.  Each time I change my ebuild, when I
> issue the "ebuild qcad-<vers>.ebuild install", I get a message stating
> that the ebuild changed.  The working directory is erased.  As a
> consequence of this, I have to watch my application be rebuilt (which
> takes a few minutes).  
> 
> So, is there a way, when testing an ebuild, to force ebuild, the
> application, NOT to rebuild the entire application.  I looked through
> the manpage and the portage HOWTO, but I didn't see anything obvious.
> 
> Thanks for the assistance,
> 
> 

-- 
Using the internet as it was originally intended...
for the further research of pornography and pipebombs.

Re: [gentoo-dev] How to test ebuild install without recompiling?

[George Shapovalov]

Edit your /etc/make.conf file and make sure that you have the line:
FEATURES="sandbox noauto"
You might want to put more stuff in that line, read description in make.conf.

George


On Friday 12 April 2002 12:34, Eric F Sorton wrote:
> Hi All,
>
> I am in the process of creating an ebuild for "qcad".
>
> The "build" step was created in short order.  The "install" step is,
> however, giving me problems.  Currently, my biggest holdup is the cycle
> time to test changes to my ebuild.  Each time I change my ebuild, when I
> issue the "ebuild qcad-<vers>.ebuild install", I get a message stating
> that the ebuild changed.  The working directory is erased.  As a
> consequence of this, I have to watch my application be rebuilt (which
> takes a few minutes).
>
> So, is there a way, when testing an ebuild, to force ebuild, the
> application, NOT to rebuild the entire application.  I looked through
> the manpage and the portage HOWTO, but I didn't see anything obvious.
>
> Thanks for the assistance,