From owner-freebsd-current Sun Feb 27 10:15: 7 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.ginko.net (mail.ginko.net [212.202.73.2]) by hub.freebsd.org (Postfix) with SMTP id A937237B526 for ; Sun, 27 Feb 2000 10:14:57 -0800 (PST) (envelope-from freebsd@tavari.de) Received: (qmail 7202 invoked from network); 27 Feb 2000 18:14:53 -0000 Received: from port0809.fra.ginko.net (HELO tavari.muc.de) (212.202.69.47) by mail.ginko.net with SMTP; 27 Feb 2000 18:14:53 -0000 Received: (from uucp@localhost) by tavari.muc.de (8.8.8/8.8.7) id TAA16583; Sun, 27 Feb 2000 19:14:04 +0100 (CET) Received: from aleisha.tavari.muc.de(192.168.42.102), claiming to be "192.168.42.102" via SMTP by smptd, id smtpdm16581; Sun Feb 27 19:14:01 2000 Date: Sun, 27 Feb 2000 19:13:08 +0100 From: Lutz Albers To: "Daniel O'Connor" , Chuck Robey Cc: freebsd-current@FreeBSD.ORG, Maxim Sobolev , bwoods2@uswest.net, Joel Ray Holveck , Will Andrews , Alex Zepeda Subject: Re: kdelibs port broken? Message-ID: <2491015814.951678788@[192.168.42.102]> In-Reply-To: X-Mailer: Mulberry/2.0.0b11 (Win32) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG If memory serves me right, Daniel O'Connor said on 2000-02-27 23:43 +1030: > On 27-Feb-00 Chuck Robey wrote: >> fine example, tho. We break the location of the config files that all >> tcl >> packages rely upon to build, for the purpose of allowing folks to run >> multiple versions simultaneously. Tcl isn't the only one like that, >> either. Anyone who wants to be able to build other tcl software that >> isn't derived from a port would be well advised to avoid using our port. > > This is done because none of those programs/libs developed a system on > their own which allowed multiple versions to be on the same machine OR > made SURE that they where backward compatible.. It's possible to run multiple versions of these kind of software on your machine. There are tools out there (i.e. modules www.modules.org) which allow this kind of operating. > Its not the ports collection thats at fault, the people who did it this > way are cleaning up the mess made by other coders. As nice as the ports collections usually is, it's simply not adequate to handle multiple versions of the same software on the same machine. lutz albers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message