From: Daniel Robbins <drobbins@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Testing *true* transparent .so updates
Date: Sat, 22 Dec 2001 12:29:18 -0600 [thread overview]
Message-ID: <20011222122918.B28064@chiba.3jane.net> (raw)
In-Reply-To: <0GOR00LJWCLM2U@mxout1.netvision.net.il>
On Sat, Dec 22, 2001 at 08:02:28PM +0200, Dan Armak wrote:
> I'll test it overnight. I haven't been following the revisions/discussion
> thuogh, so I've a question - will this support upgrading to another glibc
> version (e.g. to 2.4.5 whenever that comes out) or is it just for new
> revisions of the ebuild?
As long as the new versions of glibc will be binary compatible (and generally,
they are), then it will work for new versions as well. A few problem programs
may need to be recompiled after a major version jump, but not many.
Best Regards,
--
Daniel Robbins <drobbins@gentoo.org>
Chief Architect/President http://www.gentoo.org
Gentoo Technologies, Inc.
next prev parent reply other threads:[~2001-12-22 18:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-22 18:03 [gentoo-dev] Testing *true* transparent .so updates Daniel Robbins
2001-12-22 18:02 ` Dan Armak
2001-12-22 18:29 ` Daniel Robbins [this message]
2001-12-22 22:13 ` Dan Armak
2001-12-23 5:08 ` Daniel Robbins
2001-12-23 22:20 ` Martin Schlemmer
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=20011222122918.B28064@chiba.3jane.net \
--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