Age | Commit message (Collapse) | Author | Files | Lines |
|
in the process. (More information on tech-pkg.)
Bump PKGREVISION and BUILDLINK_DEPENDS of all packages using libtool and
installing .la files.
Bump PKGREVISION (only) of all packages depending directly on the above
via a buildlink3 include.
|
|
allowed by GCC with -pedantic -ansi. Bump the PKGREVISION.
|
|
The expat-1.95.6nb1 package has libexpat.so.4.0
and expat-1.95.7 has libexpat.so.5.0.
I noticed this because I had a fontconfig package built against
libexpat.so.4 which installed fine on another box
with expat-1.95.7 (libexpat.so.5). The fontconfig package
should have required the expat as now available in pkgsrc.
Please note that I have not bumped PKGREVISIONs for all
the packages depending on this.
|
|
built-in or not into a separate builtin.mk file. The code to deal
checking for built-in software is much simpler to deal with in pkgsrc.
The buildlink3.mk file for a package will be of the usual format
regardless of the package, which makes it simpler for packagers to
update a package.
The builtin.mk file for a package must define a single yes/no variable
USE_BUILTIN.<pkg> that is used by bsd.buildlink3.mk to decide whether
to use the built-in software or to use the pkgsrc software.
|
|
|
|
environment overrides all other settings.
|
|
|
|
|
|
|
|
the normal case when BUILDLINK_DEPENDS.<pkg> isn't specified, it receives
a value only once due to the multiple inclusion protection in the
bulldlink3.mk files. In the case where a package includes several
buildlink3.mk files that each want a slightly different version of another
dependency, having BUILDLINK_DEPENDS.<pkg> be a list allows for the
strictest <pkg> dependency to be matched.
|
|
recommended by seb :)
|
|
|
|
buildlink3 framework.
|