From: "Sean P. Kane" <spkane@genomatica.com>
To: "Dustin Knie" <dustin@attbi.com>, <gentoo-dev@gentoo.org>
Subject: RE: [gentoo-dev] Recompile but NOT upgrade
Date: Fri, 3 May 2002 08:49:46 -0700 [thread overview]
Message-ID: <C42D120999B1CC4C886B6BB2832F356019B2E3@HERMES.genomatica.com> (raw)
I figured out a few things that will help, but haven't spent more then a few minutes on it so far. It looks like to build a specific ebuild you need to feed it to emerge like this:
emerge sys-apps/less/less-358-r3.ebuild
So, taking the output of '/usr/lib/portage/bin/pkglist | sort' which gives you lines like:
sys-apps/less-358-r3
sys-apps/net-tools-160-r1
And then modifying them to look like:
sys-apps/less/less-358-r3.ebuild
sys-apps/net-tools/net-tools-160-r1.ebuild
Doing an "emerge -p" on them letting people "ok" or even add and remove some things at this point.....Then do the real thing. There may be an order that is wise here. I.e. gcc first......
Sean
-----Original Message-----
From: Dustin Knie [mailto:dustin@attbi.com]
Sent: Thursday, May 02, 2002 20:18
To: gentoo-dev@gentoo.org
Cc: Sean P. Kane
Subject: Re: [gentoo-dev] Recompile but NOT upgrade
I recently started using gentoo, and love it. I'm working on learning the ebuild, emerge and portage system right now, and I'll see if I can figure out how to do something like this. I figure it'll be a great way to learn the system, and give back to the community!!!!
I'm not gonna guarentee anything, but I'll see what I can do.
Dustin Knie
On Fri, 3 May 2002, Bjarke [iso-8859-1] Sørensen wrote:
> On Thu, May 02, 2002 at 01:25:31PM -0700, Sean P. Kane wrote:
> > Is this something that anyone is considering doing in portage or
> > would it be worth trying to write a script to handle this?
>
> Writing a script, will help a lot of people now.
>
> Waiting for such in Portage wont.
> Portage has other issues right now that have to dealt with first
> (IMHO).
>
> Tell us what you'll do :)
> --
> | 9000.WASD
> |
> | Bjarke Sørensen
> | http://wasd.dk/
> |
> | There are 10 types of people in this world:
> | Those who understand binary, and those who don't.
> _______________________________________________
> gentoo-dev mailing list
> gentoo-dev@gentoo.org
> http://lists.gentoo.org/mailman/listinfo/gentoo-dev
>
next reply other threads:[~2002-05-03 15:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-03 15:49 Sean P. Kane [this message]
2002-05-03 16:55 ` [gentoo-dev] Recompile but NOT upgrade Chad M. Huneycutt
2002-05-03 20:40 ` Zach Forrest
2002-05-03 21:42 ` Bjarke Sørensen
-- strict thread matches above, loose matches on Subject: below --
2002-05-02 20:25 Sean P. Kane
2002-05-02 21:55 ` Ian Smith
2002-05-02 22:00 ` Bjarke Sørensen
2002-05-03 3:18 ` Dustin Knie
2002-05-02 15:08 Sean P. Kane
2002-05-02 18:49 ` Ian Smith
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=C42D120999B1CC4C886B6BB2832F356019B2E3@HERMES.genomatica.com \
--to=spkane@genomatica.com \
--cc=dustin@attbi.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