From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 4.0.0 (2022-12-14) on finch.gentoo.org X-Spam-Level: X-Spam-Status: No, score=-0.1 required=5.0 tests=DMARC_NONE,MAILING_LIST_MULTI autolearn=unavailable autolearn_force=no version=4.0.0 Received: from volumehost.com (volumehost.com [216.63.158.9]) by chiba.3jane.net (Postfix) with ESMTP id 791BB2016061 for ; Fri, 12 Apr 2002 14:50:00 -0500 (CDT) Received: from localhost (jhhudso@localhost) by volumehost.com (8.11.6/linuxconf) with ESMTP id g3CJnuX21769; Fri, 12 Apr 2002 14:49:56 -0500 Date: Fri, 12 Apr 2002 14:49:56 -0500 (CDT) From: "Jared H. Hudson" To: Eric F Sorton Cc: gentoo-dev@gentoo.org Subject: Re: [gentoo-dev] How to test ebuild install without recompiling? In-Reply-To: <20020412193416.GA32215@cfl.rr.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: gentoo-dev-admin@gentoo.org Errors-To: gentoo-dev-admin@gentoo.org X-BeenThere: gentoo-dev@gentoo.org X-Mailman-Version: 2.0.6 Precedence: bulk Reply-To: gentoo-dev@gentoo.org List-Help: List-Post: List-Subscribe: , List-Id: Gentoo Linux developer list List-Unsubscribe: , List-Archive: X-Archives-Salt: 8c63539d-3076-412f-b16c-7203dbe0ce95 X-Archives-Hash: 2e1131fd7cf7238a8b4560a2cbcbfeda 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-.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.