From owner-freebsd-current Thu Oct 3 11: 4:40 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 41AC437B401; Thu, 3 Oct 2002 11:04:39 -0700 (PDT) Received: from tomts11-srv.bellnexxia.net (tomts11.bellnexxia.net [209.226.175.55]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1F2CF43E4A; Thu, 3 Oct 2002 11:04:38 -0700 (PDT) (envelope-from matt@gsicomp.on.ca) Received: from xena.gsicomp.on.ca ([65.95.176.54]) by tomts11-srv.bellnexxia.net (InterMail vM.5.01.04.19 201-253-122-122-119-20020516) with ESMTP id <20021003180437.YFBP23451.tomts11-srv.bellnexxia.net@xena.gsicomp.on.ca>; Thu, 3 Oct 2002 14:04:37 -0400 Received: from hermes (hermes.gsicomp.on.ca [192.168.0.18]) by xena.gsicomp.on.ca (8.11.3/8.11.3) with SMTP id g93Gibp14388; Thu, 3 Oct 2002 12:44:37 -0400 (EDT) (envelope-from matt@gsicomp.on.ca) Message-ID: <00ae01c26b07$55e884c0$1200a8c0@gsicomp.on.ca> From: "Matthew Emmerton" To: "Poul-Henning Kamp" , "Garance A Drosihn" Cc: "Sheldon Hearn" , , References: <3632.1033651189@critter.freebsd.dk> <007f01c26ae2$09b11ab0$1200a8c0@gsicomp.on.ca> Subject: Re: expat2 in the base system? Date: Thu, 3 Oct 2002 14:04:36 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4807.1700 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > At 9:37 AM -0400 10/3/02, Matthew Emmerton wrote: > > > Garance A Drosihnwrites: > >> > >> >I think it would be very prudent that any base-system expat have > > > >it's own name, even if it's just "expat2fb". > > > > >> It sounds to me like this sums it up nicely. The thing about it > >> I like is that it does not prevent us from taking the other route > >> later on, whereas putting an "official-looking" expat in the tree > > > and yanking that later would be a mess. > > > >Well, playing the devil's advocate -- isn't this the type of > >discussion the preceeded the introduction of Perl into the base > >system, the introduction of which created such a mess that we > >finally took Perl out of the base system in -CURRENT? > > The point is that we installed perl as 'perl - the official perl'. > We then got into trouble when new versions of perl came out, and > users argued which version should be the official one. That is > exactly what we should try to avoid when bringing in expat2, and > why I think it should be brought in under an alternate name. > > The official expat2 is not something we control. The present > version of expat2 would be useful for parts of the base system, > but we're bringing it in *for* the base system, and not "as a > convenience for users". Thus, let's pick a name which will not > conflict with the port. If the name does not conflict with the > port, then we should not see the problems that we had with perl. Agreed. If we name it something other than 'expat', then the ports should never see it and the users should never get confused. If this was part of the original proposal, then I missed it entirely. -- Matt Emmerton To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message