From owner-freebsd-current Wed Mar 6 03:45:07 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id DAA13959 for current-outgoing; Wed, 6 Mar 1996 03:45:07 -0800 (PST) Received: from grumble.grondar.za (root@grumble.grondar.za [196.7.18.130]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id DAA13953 for ; Wed, 6 Mar 1996 03:45:01 -0800 (PST) Received: from grumble.grondar.za (mark@localhost [127.0.0.1]) by grumble.grondar.za (8.7.4/8.7.3) with ESMTP id NAA29815; Wed, 6 Mar 1996 13:43:47 +0200 (SAT) Message-Id: <199603061143.NAA29815@grumble.grondar.za> To: "Jordan K. Hubbard" cc: Mark Murray , joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch), freebsd-current@FreeBSD.org (FreeBSD-current users) Subject: Re: 2.2-960226-SNAP now on ftp.freebsd.org Date: Wed, 06 Mar 1996 13:43:47 +0200 From: Mark Murray Sender: owner-current@FreeBSD.org Precedence: bulk "Jordan K. Hubbard" wrote: > > Why are we carrying some of this crap? Ok I know why we need the old > > shared libraries, but there is a libgcc.so.261.0 in the distribution > > that really aught to go in the libcompat set? Let me know what is > > involved in broad terms and I'll look at it. > > Well, as to why, I guess backwards compatibility. People want to > continue running their old bins. If there's something from a previous > release that needs to go into a new one in order to support this, > there's the start of a compat dist. The libgcc.so.261.0 was a special > case because Poul-Henning didn't feel like rolling a compat205 > distribution with only one file in it.. :-) Proposal: why do we not just get all of them - libc.so.2.2, libgcc.so.261.0 etc and make one compat2.n out of them (or is that done already?)? I'll do it if you fill me in on what you did... M -- Mark Murray 46 Harvey Rd, Claremont, Cape Town 7700, South Africa +27 21 61-3768 GMT+0200 Finger mark@grondar.za for PGP key