From: <drobbins@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] ebuild remerge
Date: Sun Feb 11 16:06:02 2001 [thread overview]
Message-ID: <20010211160531.A32617@cvs.gentoo.org> (raw)
In-Reply-To: <20010211125818.A31763@cvs.gentoo.org>; from pete@gentoo.org on Sun, Feb 11, 2001 at 12:58:18PM -0700
On Sun, Feb 11, 2001 at 12:58:18PM -0700, Pete Gavin wrote:
> Hi,
>
> I was thinking, suppose you decided to remerge gcc, and the version
> you already had installed had all the platform dependent stuff in
> /usr/lib/gcc-lib/i486-pc-linux-gnu, but when you recompile it, it
> wants to put everything in /usr/lib/gcc-lib/i686-pc-linux-gnu. This
> means that if you do ebuild remerge, you'll still have stuff hanging
> around in /usr/lib/gcc-lib/i486-pc-linux-gnu. I think the best way to
> avoid this would be to make it so a remerge saves the old contents
> list and then does a safe unmerge on it after merging the new one. I
> can't think of a pretty way to do this, tho... Do you have any ideas?
You hit the nail on the head, and this will be how it will work with
version 1.0 of Gentoo Linux.
Best Regards,
--
Daniel Robbins <drobbins@gentoo.org>
President/CEO http://www.gentoo.org
Gentoo Technologies, Inc.
prev parent reply other threads:[~2001-02-11 23:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-11 12:59 [gentoo-dev] ebuild remerge Pete Gavin
2001-02-11 14:32 ` Achim Gottinger
2001-02-11 16:06 ` drobbins [this message]
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=20010211160531.A32617@cvs.gentoo.org \
--to=drobbins@gentoo.org \
--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