Re: xlib6g and emacs (and others)
- To: Joey Hess <firstname.lastname@example.org>
- Cc: email@example.com, joost witteveen <firstname.lastname@example.org>
- Subject: Re: xlib6g and emacs (and others)
- From: David Engel <email@example.com>
- Date: Tue, 9 Sep 1997 15:46:07 -0500
- Message-id: <19970909154607.07717@elo>
- In-reply-to: <19970909162857.17000@kite>; from Joey Hess on Tue, Sep 09, 1997 at 04:28:57PM -0400
- References: <firstname.lastname@example.org> <19970909091928.28424@elo> <19970909152855.14949@kite> <19970909143041.49086@elo> <19970909153320.21932@kite> <19970909151205.64319@elo> <19970909162857.17000@kite>
On Tue, Sep 09, 1997 at 04:28:57PM -0400, Joey Hess wrote:
> yeah, I uploaded a libc6 version yesterday. Somehow (magically), libc6 now
> shows up in the ldd of the library too. I didn't fix that by hand, so dunno
> how that got there. :-)
I dunno either but it's there. See below why this may not be good.
> Something else I've ben wondering about is if I ned something like a
> newxtawg package that is libc6, and keep a nextaw that is libc5. I really
> hope not. I've noticed that libc5 programs work ok with the new libc6
> nextaw, but I guess this may not be a good idea.
You may want both a nextaw and a nextawg package. Since the new
nextaw has an explicit dependency on libc6, libc5 programs will no
longer use it. I doubt this is what you intended.
David Engel ODS Networks
email@example.com 1001 E. Arapaho Road
(972) 234-6400 Richardson, TX 75081
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
Trouble? e-mail to firstname.lastname@example.org .