From owner-freebsd-current Wed Feb 14 12:17:22 2001 Delivered-To: freebsd-current@freebsd.org Received: from mail.gmx.net (mail.gmx.net [194.221.183.20]) by hub.freebsd.org (Postfix) with SMTP id E927A37B503 for ; Wed, 14 Feb 2001 12:17:10 -0800 (PST) Received: (qmail 15544 invoked by uid 0); 14 Feb 2001 20:17:10 -0000 Received: from pd9508803.dip.t-dialin.net (HELO speedy.gsinet) (217.80.136.3) by mail.gmx.net (mp002-rz3) with SMTP; 14 Feb 2001 20:17:10 -0000 Received: (from sittig@localhost) by speedy.gsinet (8.8.8/8.8.8) id VAA15636 for freebsd-current@FreeBSD.ORG; Wed, 14 Feb 2001 21:10:04 +0100 Date: Wed, 14 Feb 2001 21:10:04 +0100 From: Gerhard Sittig To: freebsd-current@FreeBSD.ORG Subject: Re: Patch for FILE problems (was Re: -CURRENT is bad for me...) Message-ID: <20010214211004.A15618@speedy.gsinet> Mail-Followup-To: freebsd-current@FreeBSD.ORG References: <200102130120.f1D1KpU56194@mobile.wemm.org> <200102130131.f1D1VrW33790@harmony.village.org> <3A895FA0.25EBC727@originative.co.uk> <20010213131802.B79651@dragon.nuxi.com> <3A89D5BF.D46B8FCC@originative.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <3A89D5BF.D46B8FCC@originative.co.uk>; from paul@originative.co.uk on Wed, Feb 14, 2001 at 12:47:59AM +0000 Organization: System Defenestrators Inc. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Feb 14, 2001 at 00:47 +0000, Paul Richards wrote: > > To be honest, DLLs are better than our scheme from that > perspective. While you might screw a load of applications by > upgrading a DLL with the same name you can at least look at the > version number in the properties to find out which version of > that DLL it is. There's no way of looking at a libc.so.5 and > say which version of libc.so.5 it is. Although `ident` does > provide a slightly cumbersome way of getting some information > to help with that when you really need it. But isn't this aspect something a project creating its own libc can solve by itself regardless of the executable format the library is held in? You're always free to introduce a version query function returning the necessary info to the app. And storing this information in an ASCII frame in the code while separating the pure number upon (logical) query you can do something in userland, too, like "strings $LIB | grep 'LibVersion'". Admittedly it's not elegant neither is it done with system tools like "executable properties". But it should work. And it's your or our lib (depending on how you look at it) -- do with it whatever you want to ... :) And why does it remind me of "you cannot tell the config used for compilation from looking at a kernel image, without watching it run and probe your machine and still having some possibility of errors / misses"? That's BTW where I feel that INCLUDE_CONFIG_FILE should be a default option. Why not just stick this info into the resulting binary if you depend on knowing it later and cost is acceptable if not unnoticable? virtually yours 82D1 9B9C 01DC 4FB4 D7B4 61BE 3F49 4F77 72DE DA76 Gerhard Sittig true | mail -s "get gpg key" Gerhard.Sittig@gmx.net -- If you don't understand or are scared by any of the above ask your parents or an adult to help you. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message