=2D----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Sun, 4 Jan 2004 04:43 pm, Rene Hexel wrote:
> On 04/01/2004, at 2:39 PM, Michal Pasternak wrote:
> > changes). How can I know, what versions it will be incompatible with
> > in the
> > *future* ?
>
>    I'm not talking about the future.  I'm talking about the past.
>
>    If you update, e.g., libtiff to 3.6.1, you know that it's
> incompatible with 3.5.5 or lower.  Therefore binary packages
> that depend on libtiff that were compiled against 3.5.5 won't
> link against libtiff-3.6.1 (because it has an
> INCOMPATIBLE_WITH<=3D3.5.5 entry).
>
> > How would INCOMPATIBLE_WITH solve the problem Jeremy had?
>
>    See above.  If libtiff-3.6.1 has an INCOMPATIBLE_WITH
> entry for lower versions of libtiff, binaries compiled
> against these older versions would no longer install
> with a newer libtiff installed.

Another problem that I see is that package maintainer are too keenly settin=
g=20
BUILDLINK_DEPENDS.xxxx in the buildlink2.mk files to the current revision=20
level, although, applications  may not necessarily require it if backward=20
compatibility is ensured..

cheerio Berndt
=2D --=20
Name	: Berndt Josef Wulf		| +++ With BSD on Packet Radio +++
E-Mail	: wulf at ping dot net dot au	|    tfkiss, tnt, dpbox, wampes
ICQ	: 18196098			|  VK5ABN, Nairne, South Australia=20
URL	: http://www.ping.net.au/~wulf	| MBOX : vk5abn@vk5abn.#lmr.#sa.au.oc
Sysinfo	: DEC Miata 500AU, NetBSD-1.6ZF	| BBS  : vk5abn.#lmr.#sa.aus.oc=20
=2D----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (NetBSD)

iD8DBQE/9/CMcUIHpeIRpjERAgDZAKCZ4NJnGVXjB0iALb0u23EXkbqvEwCg0Yvd
LCXmUF9xykBl8HopCrswZ6I=3D
=3D7f2R
=2D----END PGP SIGNATURE-----