From: Eric F Sorton <erics@cfl.rr.com>
To: gentoo-dev@gentoo.org
Subject: [gentoo-dev] How to test ebuild install without recompiling?
Date: Fri, 12 Apr 2002 15:34:16 -0400 [thread overview]
Message-ID: <20020412193416.GA32215@cfl.rr.com> (raw)
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>
next reply other threads:[~2002-04-12 19:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-12 19:34 Eric F Sorton [this message]
2002-04-12 19:49 ` [gentoo-dev] How to test ebuild install without recompiling? Jared H. Hudson
2002-04-12 23:40 ` George Shapovalov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020412193416.GA32215@cfl.rr.com \
--to=erics@cfl.rr.com \
--cc=gentoo-dev@gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox