PKGLOCALEDIR and which install their locale files directly under
${PREFIX}/${PKGLOCALEDIR} and sort the PLIST file entries. From now
on, pkgsrc/mk/plist/plist-locale.awk will automatically handle
transforming the PLIST to refer to the correct locale directory.
RECOMMENDED is removed. It becomes ABI_DEPENDS.
BUILDLINK_RECOMMENDED.foo becomes BUILDLINK_ABI_DEPENDS.foo.
BUILDLINK_DEPENDS.foo becomes BUILDLINK_API_DEPENDS.foo.
BUILDLINK_DEPENDS does not change.
IGNORE_RECOMMENDED (which defaulted to "no") becomes USE_ABI_DEPENDS
which defaults to "yes".
Added to obsolete.mk checking for IGNORE_RECOMMENDED.
I did not manually go through and fix any aesthetic tab/spacing issues.
I have tested the above patch on DragonFly building and packaging
subversion and pkglint and their many dependencies.
I have also tested USE_ABI_DEPENDS=no on my NetBSD workstation (where I
have used IGNORE_RECOMMENDED for a long time). I have been an active user
of IGNORE_RECOMMENDED since it was available.
As suggested, I removed the documentation sentences suggesting bumping for
"security" issues.
As discussed on tech-pkg.
I will commit to revbump, pkglint, pkg_install, createbuildlink separately.
Note that if you use wip, it will fail! I will commit to pkgsrc-wip
later (within day).
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.
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.
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".
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.
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!
_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".]
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.
Changes include:
2001-03-11 Havoc Pennington <hp@redhat.com>
* configure.in: 1.0.0, woo-hoo!
2001-03-06 Havoc Pennington <hp@redhat.com>
* configure.in: bump version to 0.51
* gconf/gconfd.c (gconf_main): change the periodic timeout to 15
minutes, to be a bit more aggressive about cleanup.
(open_append_handle): add a timeout to close the
saved_state filehandle after a short time, to avoid keeping
descriptors open.
(gconfd_need_log_cleanup): new internal function used to control
whether the periodic cleanup function needs to save a log file
2001-02-27 Havoc Pennington <hp@redhat.com>
* gconf.spec.in: %define prefix %{_prefix} instead of @prefix@
2001-02-27 Havoc Pennington <hp@redhat.com>
* configure.in: bump version to 0.50
* gconf/gconfd.c (main): Close stdin/stdout/stderr. Also, set the
log handler, so we don't need stdout/stderr to see GLib messages,
they go to syslog.
* configure.in: Turn off debugging by default
* gconf/Makefile.am (INCLUDES): set the log domain
* gconf/gconftool.c (recurse_subdir_list): the list contains full
directory paths to start with, fix from Colm
* gconf/gconfd.c (register_database): bugfix from Colm
* gconf/gconf.c (lookup_engine): fix from Colm to check that we
have an engines hash
(gconf_engine_get_for_address): improve warning message, fix from
Colm
(gconf_engine_remove_dir): new function from Colm, this was
implemented on the server side but somehow never exported.
* gconf/gconf-database.c (gconf_database_get_persistent_name): Fix
from Colm to handle the case of empty databases (no sources).
2001-02-12 Stanislav Visnovsky <visnovsky@nenya.ms.mff.cuni.cz>
* configure.in: Added sk to ALL_LINGUAS.
2001-02-05 Havoc Pennington <hp@redhat.com>
File permissions fixes, problem pointed out by Steve Fox.
* backends/xml-dir.c (dir_sync): chmod() the XML file after
xmlSaveFile creates it
* gconf/gconfd.c (main): following Stevens advice for daemons, we
were calling umask(0), change to umask(022). We need a predictable
umask, but a safer one would be good since this is a per-user
daemon not a system daemon.
* backends/dir-utils.c (mode_t_to_mode): make this more portable,
for paranoia
* backends/xml-dir.c (dir_load): We were getting directory
permissions from the %gconf.xml file, instead of from the XML root
directory. Fix.
2001-02-01 Szabolcs Ban <shooby@gnome.hu>
* configure.in: Added lang Hungarian.
* po/hu.po: Added.
2001-01-21 Havoc Pennington <hp@pobox.com>
* backends/xml-entry.c (schema_subnode_extract_data): don't warn
about <local_schema> with no locale field, because that's normal
for the default case
(schema_node_extract_value): use <local_schema> with no locale
if it exists and we don't find anything better
* tests/testschemas.c (check_schema_use): fix indentation and mem
leaks
* gconf/gconftool.c (do_get): print default value from schema
* configure.in: Bump version to 0.12
first component is now a package name+version/pattern, no more
executable/patchname/whatnot.
While there, introduce BUILD_USES_MSGFMT as shorthand to pull in
devel/gettext unless /usr/bin/msgfmt exists (i.e. on post-1.5 -current).
Patch by Alistair Crooks <agc@netbsd.org>
Convert most MESSAGE files to new syntax (${VARIABLE} gets replaced,
not @VARIABLE@, nor @@VARIABLE@@).
By default, substitutions are done for LOCALBASE, PKGNAME, PREFIX,
X11BASE, X11PREFIX; additional patterns can be added via MESSAGE_SUBST.
Clean up some packages while I'm there; add RCS tags to most MESSAGEs.
Remove some uninteresting MESSAGEs.
out of date - it was based on a.out OBJECT_FMT, and added entries in the
generated PLISTs to reflect the symlinks that ELF packages uses. It also
tried to be clever, and removed and recreated any symbolic links that were
created, which has resulted in some fun, especially with packages which
use dlopen(3) to load modules. Some recent changes to our ld.so to bring
it more into line with other Operating Systems also exposed some cracks.
+ Modify bsd.pkg.mk and its shared object handling, so that PLISTs now contain
the ELF symlinks.
+ Don't mess about with file system entries when handling shared objects in
bsd.pkg.mk, since it's likely that libtool and the BSD *.mk processing will
have got it right, and have a much better idea than we do.
+ Modify PLISTs to contain "ELF symlinks"
+ On a.out platforms, delete any "ELF symlinks" from the generated PLISTs
+ On ELF platforms, no extra processing needs to be done in bsd.pkg.mk
+ Modify print-PLIST target in bsd.pkg.mk to add dummy symlink entries on
a.out platforms
+ Update the documentation in Packages.txt
With many thanks to Thomas Klausner for keeping me honest with this.
