| 1 |
I believe you can edit your /etc/make.conf and add the word, noauto |
| 2 |
to the FEATURES= line. I would add sandbox as well, since that's in the |
| 3 |
default FEATURES line in /etc/make.globals and will be overwritten. |
| 4 |
So, you'll have something like: |
| 5 |
|
| 6 |
FEATURES="sandbox noauto" |
| 7 |
|
| 8 |
In case you're curious, the reason why it's re-compiling is that |
| 9 |
whenever you run ebuild package install, it goes through all the steps |
| 10 |
leading up to install (unless the noauto keyword is in there). |
| 11 |
|
| 12 |
In this case since you've modified the ebuild its mtime is greater than |
| 13 |
the uncompiled source, so when it does the unpack step it re-unpacks it |
| 14 |
and therefore has to re-compile it. |
| 15 |
|
| 16 |
-Jared H. |
| 17 |
|
| 18 |
On Fri, 12 Apr 2002, Eric F Sorton wrote: |
| 19 |
|
| 20 |
> Hi All, |
| 21 |
> |
| 22 |
> I am in the process of creating an ebuild for "qcad". |
| 23 |
> |
| 24 |
> The "build" step was created in short order. The "install" step is, |
| 25 |
> however, giving me problems. Currently, my biggest holdup is the cycle |
| 26 |
> time to test changes to my ebuild. Each time I change my ebuild, when I |
| 27 |
> issue the "ebuild qcad-<vers>.ebuild install", I get a message stating |
| 28 |
> that the ebuild changed. The working directory is erased. As a |
| 29 |
> consequence of this, I have to watch my application be rebuilt (which |
| 30 |
> takes a few minutes). |
| 31 |
> |
| 32 |
> So, is there a way, when testing an ebuild, to force ebuild, the |
| 33 |
> application, NOT to rebuild the entire application. I looked through |
| 34 |
> the manpage and the portage HOWTO, but I didn't see anything obvious. |
| 35 |
> |
| 36 |
> Thanks for the assistance, |
| 37 |
> |
| 38 |
> |
| 39 |
|
| 40 |
-- |
| 41 |
Using the internet as it was originally intended... |
| 42 |
for the further research of pornography and pipebombs. |
Archives