From: Brian Harring <ferringb@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Gentoo as a development platform
Date: Sat, 16 Apr 2005 21:26:51 -0500 [thread overview]
Message-ID: <20050417022651.GF13053@exodus.wit.org> (raw)
In-Reply-To: <4261BE5D.4000104@gentoo.org>
On Sat, Apr 16, 2005 at 06:39:41PM -0700, Donnie Berkholz wrote:
> Daniel Drake wrote:
> > - I'm manually configuring a package that I want installed in ebuild-fashion.
> > I know when an ebuild runs econf it passes many configure parameters to
> > achieve this (installation into /var/tmp, etc.). It would be nice if I could
> > just run "econf" from the command line and still achieve this. Similarly for
> > emake. Then I can somehow tell portage I've done src_unpack and src_compile
> > manually, so I'd just like it to get on from src_install onwards.
>
> You could source whatever files contain those functions, and create the
> files telling portage it's finished certain steps. I think there's a
> .compiled, not sure about others.
You want an ebuild shell, basically? Akin to sandbox shell?
Via cvs head of portage (doesn't work without a bit o hackery for
stable)
http://dev.gentoo.org/~ferringb/ebuild-env
http://dev.gentoo.org/~ferringb/ebuild.bashrc
Give you such a shell.
Details are at http://dev.gentoo.org/~ferringb/blog/archives/2005-03.html#e2005-03-09T04_43_49.txt
~brian
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2005-04-17 2:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-16 23:36 [gentoo-dev] Gentoo as a development platform Daniel Drake
2005-04-16 23:43 ` Francesco Riosa
2005-04-17 0:07 ` Daniel Drake
2005-04-17 0:13 ` Robert Paskowitz
2005-04-17 1:03 ` Daniel Drake
2005-04-17 16:24 ` Malte S. Stretz
2005-04-19 19:35 ` Paul de Vrieze
2005-04-16 23:43 ` Brian Harring
2005-04-17 0:03 ` Daniel Drake
2005-04-17 1:39 ` Donnie Berkholz
2005-04-17 2:26 ` Brian Harring [this message]
2005-04-17 0:48 ` Jason Cooper
2005-04-17 1:14 ` Brian Harring
2005-04-17 1:38 ` Donnie Berkholz
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=20050417022651.GF13053@exodus.wit.org \
--to=ferringb@gentoo.org \
--cc=gentoo-dev@lists.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