Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
|
|
(1) The Berkeley DB storage backend requires DB-3.x, and used an
experimental feature of DB-3.x.
(2) There is a pretty severe bug that "prevents serious use of the
Berkeley DB backend", according to the documentation included
with the GConf sources.
(3) GConf2, the successor to GConf, doesn't build with the Berkeley
DB storage backend either.
Suggested by jlam.
Bump PKGREVISION.
Remove db3 bl3 inclusion from bl3 file, and bump BUILDLINK_DEPENDS
for it.
This fixes the gnucash build problems noted in PR 28423.
|
|
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.
|
|
All library names listed by *.la files no longer need to be listed
in the PLIST, e.g., instead of:
lib/libfoo.a
lib/libfoo.la
lib/libfoo.so
lib/libfoo.so.0
lib/libfoo.so.0.1
one simply needs:
lib/libfoo.la
and bsd.pkg.mk will automatically ensure that the additional library
names are listed in the installed package +CONTENTS file.
Also make LIBTOOLIZE_PLIST default to "yes".
|
|
|
|
|
|
e.g. "BUILDLINK_PKGBASE.gtk?= gtk+". This is mandated by the example
buildlink[23].mk files in bsd.buildlink[23].mk.
|
|
by moving the inclusion of buildlink3.mk files outside of the protected
region. This bug would be seen by users that have set PREFER_PKGSRC
or PREFER_NATIVE to non-default values.
BUILDLINK_PACKAGES should be ordered so that for any package in the
list, that package doesn't depend on any packages to the left of it
in the list. This ordering property is used to check for builtin
packages in the correct order. The problem was that including a
buildlink3.mk file for <pkg> correctly ensured that <pkg> was removed
from BUILDLINK_PACKAGES and appended to the end. However, since the
inclusion of any other buildlink3.mk files within that buildlink3.mk
was in a region that was protected against multiple inclusion, those
dependencies weren't also moved to the end of BUILDLINK_PACKAGES.
|
|
buildlink3.mk file in revision 1.101 of bsd.buildlink3.mk.
|
|
|
|
may be shared with GConf2 in some scenarios.
|
|
|
|
relative to ${WRKSRC}. Remove redundant LIBTOOL_OVERRIDE settings that
are automatically handled by the default setting in bsd.pkg.mk.
|
|
automatically now.
|
|
|
|
Tiff is backward compatible, but was broken on amd64 platform
so this makes sure new tiff is used.
|
|
|
|
|
|
|
|
|
|
dependency bumps.
|
|
|
|
|
|
|
|
Patch provided in PR pkg/18701 by Julio Merino <jmmv@menta.net>
|
|
|
|
|
|
|
|
buildlink2.mk files back into the main trunk.
|
|
|
|
pkgconfig cleanup.
|
|
|
|
Bump PKGREVISION
|
|
|
|
Remove `-p' from mkdir arguments, it is already part of ${MKDIR}.
While here substitute a couple of ${PREFIX} by `%D' in
`@exec ${MKDIR} ...' lines and add a couple of missing `%D' in such lines too!
|
|
|
|
properly translated for buildlink.
|
|
_never_ built, regardless of whether guile is detected or not.
* Strongly buildlinkify.
* Use LIBTOOL_OVERRIDE instead of LTCONFIG_OVERRIDE so that the correct
libtool is used during the build and installation.
* Add a pre-build target to symlink the libxml headers into ${WRKSRC} so
that references to <libxml/foo.h> will resolve to <gnome-xml/foo.h>. I
imagine that the sources will be fixed to refer to more recent header
locations in a future release of GConf.
|
|
purpose of x11.buildlink.mk is to force a package to be strongly
buildlinked, and that needs to happen on a package-by-package basis.
|
|
|
|
|
|
|
|
all dependencies on packages depending on "png" which contain shared
libraries, all for the (imminent) update to the "png" package.
[List courtesy of John Darrow, courtesy of "bulk-build".]
|
|
rmdir -> ${RMDIR}
rm -> ${RM} (${RM} added to PLIST_SUBST)
chmod -> ${CHMOD}
chown -> ${CHOWN}
|
|
Make the print-PLIST target output ${MKDIR} also.
|
|
now makes use of the real "popt" instead of the skeletion in
libgnomesupport.
|
|
|
|
pkgsrc. Instead, a new variable PKGREVISION is invented that can get
bumped independent of DISTNAME and PKGNAME.
Example #1:
DISTNAME= foo-X.Y
PKGREVISION= Z
=> PKGNAME= foo-X.YnbZ
Example #2:
DISTNAME= barthing-X.Y
PKGNAME= bar-X.Y
PKGREVISION= Z
=> PKGNAME= bar=X.YnbZ (!)
On subsequent changes, only PKGREVISION needs to be bumped, no more risk
of getting DISTNAME changed accidentally.
|
|
|