| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
Known regressions:
- "pkg_add -" (aka reading from stdin) is currently not supported
- "pkg_add -s" is not supported either
- no progress reports for the downloads
- binary packages with hardlinks created by pkg_create before
pkg_install-20080422 will not extract correctly (libarchive issue)
- no adhoc check for potential conflicts between dependencies and
already installed packages
Features:
- Twice as fast for the typical case of /var/tmp and /usr/pkg on
different filesystems
- Standalone
- implicit conflict detection before actual installation.
|
|
This switches to the new gnome-2.20 branch.
|
|
|
|
upstream name.
|
|
|
|
|
|
|
|
PKGREVISION.
|
|
|
|
USE_TOOLS+=msgfmt.
|
|
developer is officially maintaining the package.
The rationale for changing this from "tech-pkg" to "pkgsrc-users" is
that it implies that any user can try to maintain the package (by
submitting patches to the mailing list). Since the folks most likely
to care about the package are the folks that want to use it or are
already using it, this would leverage the energy of users who aren't
developers.
|
|
Bump PKGREVISION.
|
|
|
|
example MAKE_ENV+=FOO=${BAR} is changed to MAKE_ENV+=FOO=${BAR:Q}. Some
other changes are outlined in
http://mail-index.netbsd.org/tech-pkg/2005/12/02/0034.html
|
|
Several changes are involved since they are all interrelated. These
changes affect about 1000 files.
The first major change is rewriting bsd.builtin.mk as well as all of
the builtin.mk files to follow the new example in bsd.builtin.mk.
The loop to include all of the builtin.mk files needed by the package
is moved from bsd.builtin.mk and into bsd.buildlink3.mk. bsd.builtin.mk
is now included by each of the individual builtin.mk files and provides
some common logic for all of the builtin.mk files. Currently, this
includes the computation for whether the native or pkgsrc version of
the package is preferred. This causes USE_BUILTIN.* to be correctly
set when one builtin.mk file includes another.
The second major change is teach the builtin.mk files to consider
files under ${LOCALBASE} to be from pkgsrc-controlled packages. Most
of the builtin.mk files test for the presence of built-in software by
checking for the existence of certain files, e.g. <pthread.h>, and we
now assume that if that file is under ${LOCALBASE}, then it must be
from pkgsrc. This modification is a nod toward LOCALBASE=/usr. The
exceptions to this new check are the X11 distribution packages, which
are handled specially as noted below.
The third major change is providing builtin.mk and version.mk files
for each of the X11 distribution packages in pkgsrc. The builtin.mk
file can detect whether the native X11 distribution is the same as
the one provided by pkgsrc, and the version.mk file computes the
version of the X11 distribution package, whether it's built-in or not.
The fourth major change is that the buildlink3.mk files for X11 packages
that install parts which are part of X11 distribution packages, e.g.
Xpm, Xcursor, etc., now use imake to query the X11 distribution for
whether the software is already provided by the X11 distribution.
This is more accurate than grepping for a symbol name in the imake
config files. Using imake required sprinkling various builtin-imake.mk
helper files into pkgsrc directories. These files are used as input
to imake since imake can't use stdin for that purpose.
The fifth major change is in how packages note that they use X11.
Instead of setting USE_X11, package Makefiles should now include
x11.buildlink3.mk instead. This causes the X11 package buildlink3
and builtin logic to be executed at the correct place for buildlink3.mk
and builtin.mk files that previously set USE_X11, and fixes packages
that relied on buildlink3.mk files to implicitly note that X11 is
needed. Package buildlink3.mk should also include x11.buildlink3.mk
when linking against the package libraries requires also linking
against the X11 libraries. Where it was obvious, redundant inclusions
of x11.buildlink3.mk have been removed.
|
|
|
|
|
|
(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.
|
|
|
|
|
|
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.
|
|
Bump PKGREVISION
|
|
_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.
|
|
|
|
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".]
|
|
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.
|
|
redefines about which buildlink.mk files would care is BUILDLINK_X11_DIR,
which points to the location of the X11R6 hierarchy used during building.
If x11.buildlink.mk isn't included, then BUILDLINK_X11_DIR defaults to
${X11BASE} (set in bsd.pkg.mk), so its value is always safe to use. Remove
the ifdefs surrounding the use of BUILDLINK_X11_DIR in tk/buildlink.mk and
revert changes to move x11.buildlink.mk before the other buildlink.mk files.
|
|
use X11_BUILDLINK_MK as a test value. Generally just reordering the
inclusions so that x11.buildlink.mk comes before the other buildlink.mk
files will make everthing work.
|
|
|
|
Automatically install etc/gconf/1/path from etc/gconf/1/path.example if
needed (both in Makefile and PLIST), remove obsoleted MESSAGE, and fix a
path to work with xpkgwedge.
|
|
|
|
GConf-1.0.4 is required for galeon-1.20 as pointed out in private mail by
Shin'ichiro TAYA <taya@netbsd.org>
|
|
Changes are bugfixes only:
* Many robustness issues and crashes fixed
* Fixes for bugs where you end up with multiple oafd's
|
|
adapt by moving CPPFLAGS settings to top-level, and removing explicit
inclusion of CPPFLAGS into MAKE_ENV and CONFIGURE_ENV.
|
|
|
