tech-pkg archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: updating dependency BUILDLINK_API_DEPENDS




To: "Jeremy C. Reed" <reed%reedmedia.net@localhost>

Subject: Re: updating dependency BUILDLINK_API_DEPENDS

From: "Johnny C. Lam" <jlam%pkgsrc.org@localhost>

Date: Mon, 17 Mar 2008 11:28:30 -0400


Jeremy C. Reed wrote:

How can we improve the buildlinking system to not say:

        ERROR: bar is not installed; can't buildlink files.

when it is really installed?

The problem is that a dependenc
y "foo" is good enough. It has a dependency  listed in its buildlink3.mk file of "bar".

But tha
t "bar" buildlink3.mk file's BUILDLINK_API_DEPENDS.bar is higher  than the installed version of "bar".

If a package needs a higher BUIL
DLINK_API_DEPENDS than its dependencies  do, then it should explicitly include the buildlink3.mk file for that  sub-dependency. The rule should be that you should not set  BUILDLINK_API_DEPENDS.bar unless you also include bar/buildlink3.mk.

        Cheers,

        -- Johnny C. Lam


References:

updating dependency BUILDLINK_API_DEPENDS
From: Jeremy C. Reed




Prev by Date: Re: make replace broken?

Next by Date: Naming convention for Ruby packages?

Previous by Thread: updating dependency BUILDLINK_API_DEPENDS

Next by Thread: RFC: New pkglint warning for Makefile.common

Indexes:

reverse Date

reverse Thread

Old Index



Home | Main Index | Thread Index | Old Index