This update adds a prominant message at the end of the run explicitly stating
which class of NO_BIN_ON_{FTP,CDROM} pkgs have been included or excluded
from the set. This should help prevent accidental license violations.
Suggested by Hubert Feyrer in private email.
- by default cdpack now excludes NO_BIN_ON_CDROM packages. This is the most
important change. Previously all pkgs were included.
- added flag to allow NO_BIN_ON_CDROM packages
- added flag to exclude NO_BIN_ON_FTP packages
- increased the verbosity resulting from the verbose flag
- added a debug flag to preserve tmp files
* when creating BUILDLINK_CONFIG_WRAPPER_SED we also need to create
a corresponding REPLACE_BUILDLINK_SED to reverse the effects
* account for packages that set USE_X11BASE to an empty string.
* create BUILDLINK_CONFIG_WRAPPER_SED patterns if required
* interpret "Makefile.common" as well as "Makefile" for packages
that share common information
issues pointed out in private email by Thomas Klausner:
* Include $PKGVERSION instead of RCS revision in script output
* Add a few line breaks to make the output more readable
* -buildlink-config-wrapper is a hardcoded suffix in
bsd.buildlink.mk. Therefore, make sure the created config wapper
targets actually have this suffix.
* Prevent pkgconfig logic from twice including
pkgconfig/buildlink.mk
* Add missing \" in created sed rules
* Include createbuildlink revision in created files
a buildlink.mk from a package's Makefile and PLIST.
XXX: this is an attempt to make the creation of buildlink.mk files more
XXX: systematic and less error-prone than copying existing buildlink.mk
XXX: files and modifying them for a new package. Any help in making this
XXX: script less simplistic and more versatile is gladly welcome!
${PREFIX}/include/pgsql/server. Therefore:
o Change files/Makefile so that the include files are searched in both
possible locations
o Bump pkgconflict's revision to 0.3nb1
'Makefile' is back in BUILD_VERSION, so add it back in here.
Implement '-f' based on patches from norm@sandbox.org.uk - perform a
fetch for all missing/mismatched packages before any building. Can be
used with -c or -i to just fetch missing/mismatched packages.
Handle updated format of +BUILD_VERSION - sometimes patches are recorded
with paths, sometimes not. Ideally we would have a show-build-version
target in bsd.pkg.mk which could be sued by us, but that doesn't help
checking against existing installations where nothing has changed except
the way +BUILD_VERSION is formatted.
Changes summary:
- Support digital signatures in binary packages.
- Use full path name to tar.
- Fix ``pkg_add -u'' for packages without dependencies.
- Add ``-U'' and ``-I'' options to pkg_create.
- Close some memory leaks.
- Add ``-n'' argument to pkg_info to show needed packages.
- Fix pkg_info to not FTP unneccessarily
- Improve version number handling:
- recognition of "pl" ("patchlevel") and "rc" ("release candidate")
strings
- recognition of '_' and "pl" as pseudonyms for '.' (1.2pl2 == 1.2.2)
- handle alphabetic characters properly (1.2e == 1.2.5)
- 64-bit integers are used internally for each component of the version
number.
- Various internal cleanups, bugfixes, and API tweaks.
Avoid using '..' in LOCALBASE as it might end up in the binaries as part of
TAR_FULLPATHNAME.
Record MANINSTALL setting.
Add a workaround for SHLOCK definition or else LOCALBASE setting breaks it.
scripts so that they are properly added and removed if xpkgwedge is
installed as a binary package. Also, add some protection against the case
where ${X11BASE} == ${PREFIX} by checking this isn't true before removing
these font-manipulation programs.
Unconditionally set PKGSRC_LOCKTYPE to `none' to avoid bootstrapping problem.
Do not generate formatted manual and do not install source manual on Solaris or
else we would need to make this package depends on textproc/groff. IMHO this
should be avoided for this package as it can be considered a prerequisite for
building further packages.
NetBSD-current, into the NetBSD Packages Collection.
The shlock command can create or verify a lock file on behalf of a
shell or other script program. When it attempts to create a lock
file, if one already exists, shlock verifies that it is or is not
valid. If valid, shlock will exit with a non-zero exit code. If
invalid, shlock will re- move the lock file, and create a new one.
shlock uses the rename(2) system call to make the final target lock
file, which is an atomic operation (i.e. "dot locking", so named for
this mech- anism's original use for locking system mailboxes). It
puts the process ID ("PID") from the command line into the requested
lock file.
shlock verifies that an extant lock file is still valid by using
kill(2) with a zero signal to check for the existence of the process
that holds the lock.
This package is only for Solaris and Linux platforms at present.
New feature:
Somewhat rewritten to support run from top-level pkgsrc directory. When run
from there pkgcvsupdate launchs a separate cvs update for each caterory
directory. This is believed to be faster than a single cvs run. Thanks to
Simon Burge for this!
Bugfix:
First update a category Makefile (by way of a non-recursive update in the
category directory) before finding out which packages are included in it.
Adapt to 'distinfo' change.
Adapt to 'pkg' directory removal.
Automatically rename 'pkg-message' files.
Fix a problem introduced in 1.4 (which perl -w warned about).
packages, since certain arguments passed to the tar command by pkg_create
assume the existence of GNU tar (-T for one), and Darwin's standard tar
doesn't understand these.
lintpkgsrc - if we find one valid match in a DEPENDS entry, don't
bitch about any others expanding to a non-existant package:
Example: postgresql-{6.5.3*,7.0*,lib-*}
With this lintpkgsrc -d now outputs six lines on current pkgsrc.
Note to self: When you use 'cvs c^[P' the second time in an
evening for the same package... its enough.
lintpkgsrc.pl:
Finally we parse {x,y,z} constructs in DEPENDS, plus handle a
few more make conditionals. Now most of the lintpkgsrc -d output
is related to versions of software no longer in pkgsrc...
Does the fun ever start?
