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.
|
|
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".
|
|
|
|
LOCALBASE.
- Remove unnecessary references to X11BASE and LOCALBASE.
- Enable pkgviews installation.
OK'ed by tron@, the maintainer.
|
|
|
|
|
|
*-dirs packages.
|
|
"yes" and packages that can't use the DB-1.85 API should set it to "no".
This makes the native DB the preferred DB if it exists.
|
|
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.
|
|
|
|
|
|
|
|
the latest versions) xdg-dirs, xdg-x11-dirs or gnome*-dirs.
Bump PKGREVISION.
|
|
buildlink3.mk file in revision 1.101 of bsd.buildlink3.mk.
|
|
Bump PKGREVISION to 2. Found by wiz@.
|
|
shared with some other gnome2 packages in some scenarios.
|
|
relative to ${WRKSRC}. Remove redundant LIBTOOL_OVERRIDE settings that
are automatically handled by the default setting in bsd.pkg.mk.
|
|
|
|
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.
|
|
|
|
|
|
Tiff is backward compatible, but was broken on amd64 platform
so this makes sure new tiff is used.
|
|
|
|
|
|
didn't find a useful changelog, most likely it is a bugfix release only;
I'm only touching it because newer gnomemm/gnome-- want it, and
gnomemm/gnome-- needs to be fixed to compile with gcc3
|
|
|
|
|
|
the shared share/mime-info directory. Bump PKGREVISION.
|
|
|
|
|
|
dependency bumps.
|
|
either shared libraries or header files. Remove references to these
buildlink2.mk files from package Makefiles.
|
|
remove them). Bump PKGREVISION.
|
|
Also avoid possible detection of gtk-doc.
Bump PKGREVISION to 2.
|
|
|
|
|
|
replacement of "-ldb" in the configure script.
|
|
|
|
|
|
Patch provided in PR pkg/18701 by Julio Merino <jmmv@menta.net>
|
|
|
|
compiled using orbit-idl, which uses the C preprocessor to do its work, and
the C preprocessor has it's arguments transformed (correctly) by
buildlink2.
|
|
buildlink2.mk files back into the main trunk. This provides sufficient
buildlink2 infrastructure to start merging other packages from the
buildlink2 branch that have already been converted to use the buildlink2
framework.
|
|
problems under NetBSD-current.
|
|
|
|
|
|
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!
|
|
don't remove the directory unconditionally.
|
|
last update. This prevents crashes when opening URLs (i.e. by selecting
"Open in browser" in the gnome-terminal context menu)
|
|
|