cvs commit: ports/graphics/djvulibre Makefile ports/textproc/wordnet Makefile

Alexander Leidinger Alexander at Leidinger.net
Thu Jul 14 13:06:44 GMT 2005


Alexey Dokuchaev <danfe at FreeBSD.org> wrote:

> On Thu, Jul 14, 2005 at 09:44:32AM +0200, Pav Lucistnik wrote:
>> Mikhail Teterin p??e v st 13. 07. 2005 v 23:52 +0000:
>> > mi          2005-07-13 23:52:55 UTC
>> >
>> >   FreeBSD ports repository
>> >
>> >   Modified files:
>> >     graphics/djvulibre   Makefile
>> >     textproc/wordnet     Makefile
>> >   Log:
>> >   Remove the requirements for particular shared library versions on two
>> >   more ports, which I created.
>>
>> Is this something we agreed to do, or you are going as a sole man
>> against long term practice?

AFAIK it's up to the maintainer/creator of the port if he uses a particular
version number or allows every version of a library.

> I also do not like this change.  It's very convenient to see what
> happens to port with its dependencies getting particular .so version bump
> (as it can be more than just PORTREVISION++).  With your change, it's harded
> to track.

Why is it harder? If you commit an update which changes the lib version, you
have to search the ports which use it. If you e.g. committed a change to
graphics/jpeg, you can grep for "graphics/jpeg". You don't need to grep for
libjpeg.X.

If the changed lib not only has a changed ABI but also a changed API in a way
the port has to be patched, you can add the lib version at the time you
change the port. At this time the port really depends upon a particular
version, until then it doesn't.

Bye,
Alexander.

-- 
http://www.Leidinger.net  Alexander @ Leidinger.net: PGP ID = B0063FE7
http://www.FreeBSD.org     netchild @ FreeBSD.org  : PGP ID = 72077137
Moneyliness is next to Godliness.
		-- Andries van Dam




More information about the cvs-all mailing list