On Fri, 28 Jan 2005, Jeremy C. Reed wrote:

> This is what should be documented:
>
> - The BUILDLINK_DEPENDS is bumped when packages depending on it stop
> building (because of API change, for example). It should not be bumped for
> shared library naming changes (unless it has an ABI change).
>
> - BUILDLINK_RECOMMENDED should be used for SONAME changes.
>
> - BUILDLINK_RECOMMENDED should be used for for security fixes.
>
> - In the case where only one or very few packages that depend on a certain
> functionality change, then they can list the BUILDLINK_DEPENDS.${foo}
> specifically for their own build.

You've just restated my proposed criteria list (which I've restated a few
times myself), but no one has blessed it from on high yet.  8-)

> Maybe BUILDLINK_RECOMMENDED should be used for when new features are
> added? (What do you all think?)

If we rework the @blddep handling in pkg_add (being pondered in another
forum) to be a lower-bound dewey dependency, this should never be necessary,
since binary packages would then have a guaranteed minimum feature set
dependency.

> As for curl, can we revert the change and just use BUILDLINK_RECOMMENDED?

I think that's appropriate, but I am not authoritative on this issue.

-- 
-- Todd Vierling <tv@duh.org> <tv@pobox.com>