Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 09 Apr 1999 16:24:02 -0500
From:      Jacques Vidrine <n@nectar.com>
To:        Jeremy Lea <reg@shale.csir.co.za>
Cc:        ports@FreeBSD.ORG
Subject:   Re: /sys/boot, egcs vs. gcc, -Os 
Message-ID:  <199904092124.QAA91710@spawn.nectar.com>
In-Reply-To: <19990409165121.A6250@shale.csir.co.za> 
References:  <Pine.BSF.4.05.9904072109480.94006-100000@zippy.dyn.ml.org> <Pine.BSF.4.10.9904081223480.378-100000@picnic.mat.net> <19990409165121.A6250@shale.csir.co.za>

next in thread | previous in thread | raw e-mail | index | archive | help
[moving to ports@FreeBSD.ORG in the hopes that it sticks]

On 9 April 1999 at 16:51, Jeremy Lea <reg@shale.csir.co.za> wrote:
[snip]
> 1.  Use -soname for binaries.  Add this to $LDFLAGS or something, to get
>     a version number installed into a binary then create extra magic or
>     a script to test this in the DEPENDS.  I don't know if this is
>     possible, but there must be some field available which can be got
>     with either file(1) or objdump(1).  Same idea for scripts.

This isn't general enough, in that we should be able to handle e.g.
binaries in formats other than ELF, shell/perl/python/et. al. scripts,
java class files.

> 2.  Add a version history in files.  Each time a port is upgraded, add
>     the new PKGNAME to files/history.  Recreate these from the CVS
>     history using a very clever script.  Then use this to deinstall all
>     old versions, or for upgrading.  Upgrading requires much more
>     dynamic PLISTs.  Maybe a port should check for all files in PLIST
>     before installing and refuse to install unless they are cleaned out
>     first.

Maybe the PLIST should consist of more than just the filename.  We can
generalize version numbers and use them for any type of file by including
a version number in the PLIST.

bin/myportapp		version=2
lib/libmyport.so.1.2	version=3

It would be easy enough to create tools to help in generating PLISTs 
that are informative enough.  At the minimum, this would force porters
to think about version differences.  

Jacques Vidrine / n@nectar.com / nectar@FreeBSD.org


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-ports" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199904092124.QAA91710>