Return-Path: Delivered-To: apmail-apr-dev-archive@apr.apache.org Received: (qmail 38630 invoked by uid 500); 17 Sep 2002 05:58:59 -0000 Mailing-List: contact dev-help@apr.apache.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Delivered-To: mailing list dev@apr.apache.org Received: (qmail 38619 invoked from network); 17 Sep 2002 05:58:59 -0000 X-Authentication-Warning: cancer.clove.org: jerenk set sender to jerenkrantz@apache.org using -f Date: Mon, 16 Sep 2002 22:59:10 -0700 From: Justin Erenkrantz To: Pier Fumagalli Cc: dev@apr.apache.org Subject: Re: library versioning name Message-ID: <20020917055910.GQ18172@apache.org> Mail-Followup-To: Justin Erenkrantz , Pier Fumagalli , dev@apr.apache.org References: <20020916161355.B15833@lyra.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4i X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N On Tue, Sep 17, 2002 at 12:46:19AM +0100, Pier Fumagalli wrote: > Regarding headers, seriously, if I compile something today, I want it to > link against the very latest version of the library, because I want all > possible patches and updates, so I don't really see that problem... > > This document only talks about > Linux, which is a platform I luckily don't use nor know, but AFAICS, it > should work on all of them: works on FreeBSD/NetBSD, and on NetBSD it's how > EVERYTHING is compiled... For instance: You want --enable-layout=classic. =) (go read config.layout) It's my own subtle form of protest. I agree with you that Havoc's page is specifically for GNU projects and prohibits other (potentially better) forms of versioning. The GNU model is to always install things into /usr (or /usr/local). I believe that's bad form for reasons I've gone into before. This model falls flat on its face when each version has its own directory (as it needlessly complicates matters). Sadly, all of the GNU projects buy into this. Good luck trying to install anything that has automake or pkgconfig extensions in separate directories. All of those projects assume that every piece of software is in a single cluttered hierarchy. How frustrating. -- justin