diff options
author | wiz <wiz@pkgsrc.org> | 2011-08-30 15:22:35 +0000 |
---|---|---|
committer | wiz <wiz@pkgsrc.org> | 2011-08-30 15:22:35 +0000 |
commit | 5e634c465a598ef67c18b0aced2a5f0e04e1c63e (patch) | |
tree | f3cc168a60d17a2d6ad044823cc6c991d6e35aee /doc/pkgsrc.txt | |
parent | 6fd21b16130b291e48c58b1bbf26243c260d7f5b (diff) | |
download | pkgsrc-5e634c465a598ef67c18b0aced2a5f0e04e1c63e.tar.gz |
regen
Diffstat (limited to 'doc/pkgsrc.txt')
-rw-r--r-- | doc/pkgsrc.txt | 7 |
1 files changed, 3 insertions, 4 deletions
diff --git a/doc/pkgsrc.txt b/doc/pkgsrc.txt index f293e768e18..64923b650c1 100644 --- a/doc/pkgsrc.txt +++ b/doc/pkgsrc.txt @@ -4777,10 +4777,9 @@ the other binary compatibility (ABI). The difference is that a change in the API breaks compilation of programs while changes in the ABI stop compiled programs from running. -Changes to the BUILDLINK_API_DEPENDS.pkgreplaceable>varname> variable in a -buildlink3.mk file happen very rarely. One possible reason is that all packages -depending on this already need a newer version. In case it is bumped see the -description below. +Changes to the BUILDLINK_API_DEPENDS.pkg variable in a buildlink3.mk file +happen very rarely. One possible reason is that all packages depending on this +already need a newer version. In case it is bumped see the description below. The most common example of an ABI change is that the major version of a shared library is increased. In this case, BUILDLINK_ABI_DEPENDS.pkg should be |