since this shows up problems on NFS-mounted pkgsrc archives on Darwin.
On Darwin, don't try to make the po message files, since msgfmt doesn't
yet exist.
These changes allow bootstrapping the gtar-base package on Darwin.
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.
This module uses no C-coded parts in itself, but it will try to use
the Compress::Zlib module to read and write gzipped tarfiles.
Archive::Tar will still work without Zlib, it will just complain a
little bit (and, of course, not be able to use compression). The
complaining will be removed when the module leaves the alpha stage,
and can be trivially removed by commenting out the offending print
near the top of Tar.pm.
The automatic truncation in gensolpkg doesn't work for packages which
have the same package name for the first 5-6 chars.
e.g. amanda-server and amanda-client would be named amanda and amanda.
Now, we add a SVR4_PKGNAME and use amacl for amanda-client and amase for
amanda-server.
All svr4 packages also have a vendor tag, so we have to reserve some chars
for this tag, which is normaly 3 or 4 chars. Thats why we can only use 6
or 5 chars for SVR4_PKGNAME. I used 5 for all the packages, to give the
vendor tag enough room.
All p5-* packages and a few other packages have now a SVR4_PKGNAME.
cabextract is a program that un-archives files in the Microsoft
cabinet file format (.cab) or any binary file which contains an
embedded cabinet file (frequently found in .exe files).
cabextract will extract all files from all cabinet files specified on
the command line
To extract a multi-part cabinet consisting of several files, only give
the first file as an argument to cabextract as it will automatically
look for the remaining files.
Provided in PR 14259 by Ben Collver (collver@linuxfreemail.com), the
description fleshed out slightly by myself, taken from the man page.
version. I've updated devel/p5-Compress-Zlib to 1.14, which was the
level of this version, and removed this package accordingly.
Done this way because there are two other packages which depend upon
p5-Compress-Zlib being in the devel category.
The Compress::Zlib module provides a Perl interface to the zlib compression
library. Most of the functionality provided by zlib is available in
Compress::Zlib.
foo-* to foo-[0-9]*. This is to cause the dependencies to match only the
packages whose base package name is "foo", and not those named "foo-bar".
A concrete example is p5-Net-* matching p5-Net-DNS as well as p5-Net. Also
change dependency examples in Packages.txt to reflect this.
mscompress, Microsoft "compress.exe/expand.exe" compatible (de)compressor
Copyright (c) 2000 Martin Hinner <mhi@penguin.cz>
Algorithm & data structures by M. Winterhoff <100326.2776@compuserve.com>
ftp://ftp.penguin.cz/pub/users/mhi/mscompress/
This package contains two programs:
msexpand, which decompress files compressed by Microsoft compress.exe utility
(e.g. Win 3.x installation files)
mscompress, which compress files using LZ77 compression algorithm. Output
files can be decompressed using Microsoft expand.exe or msexpand(1).
Package provided by collver@linuxfreemail.com in pkg/13767, imported
without *any* modifications (an example of excellent pkgsrc work)
pkg/13900 by Don Yuniskis <auryn@gci-net.com>. The changes were based on
the suggested fix in the PR, but modified to correctly deal with
LOCALBASE =/= "/usr/pkg" case.
Bicom is a data compressor in the PPM family. It is freely available and
open source. Compression with bicom is completely bijective -- any file
is a possible bicom output that can be decompressed, and then recompressed
back to its original form. Of course, any file is also a possible bicom
input that can be compressed, and then decompressed back to its original
form.
BUILDLINK_PREFIX.<pkgname>. This allows buildlink to find X11BASE packages
regardless of whether they were installed before or after xpkgwedge was
installed. Idea by Alistair Crooks <agc@pkgsrc.org>.
FOO_REQD=1.0 being converted to foo>=1.0, one can now directly specify
the dependency pattern as FOO_DEPENDS=foo>=1.0. This allows things like
JPEG_DEPENDS=jpeg-6b, or fancier expressions like for postgresql-lib.
Change existing FOO_REQD definitions in Makefiles to FOO_DEPENDS.
Excerpt from the README file in the source code distribution:
Permission is granted to any individual or institution to use, copy, or
redistribute this software so long as all of the original files are included
unmodified, that it is not sold for profit, and that this copyright notice
is retained.
From the README file:
Oh yeah - this program may be distributed freely so long as you don't
modify it in any way. You may not charge for distributing it.
Provided in PR 12889 by Ben Collver (collver@linuxfreemail.com).
"SZDD is a weak LZSS compressor, which was used by Microsoft for many years
in their installation software - all those files with a letter taken from
the end of their extension, eg HELLO.EX_
This package includes szddexpand which will decompress szdd files.
Be careful, szddexpand overwrites the original compressed file.
Do like so: szddexpand HELLO.EX_ && mv HELLO.EX_ HELLO.EXE
SZDD was replaced with 'KWAJ' in the 1996 Microsoft Setup Toolkit. This
package does not grok the undocumented 'KWAJ' format.
One day Johnathan Forbes decided to work for Microsoft, and sold them his
LZX compression technology. So now Microsoft uses LZX compression in their
installation archives, under the guise of "CAB" files."
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>
***
NuLib is a disk and file archive program, similar in principle to PKZIP.
Instead of ZIP archives, it manipulates NuFX archives, which are usually
identified with ".SHK", ".SDK", or ".BXY".
The ".SHK" file extension is derived from ShrinkIt, the de facto
archiving standard for Apple II computers.
The 5.42 maintance release fixes more bugs and cleans up the redistribution
conditions:
- removal of unreduce.c and amiga/timelib.c code to get rid of the last
distribution restrictions beyond the BSD-like Info-ZIP LICENSE
- new generic timelib replacement (currently used by AMIGA port)
- more reasonable mapping rules of UNIX "leading-dot" filenames to the
DOS 8.3 name convention
- repaired screensize detection in MORE paging code
(was broken for DOS/OS2/WIN32 in 5.41)
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.
exportable now), using latest crypto add-on sources.
Update main distribution site and homepage.
Remove CRYPTO line (not strong cryptography).
Bump to 2.3nb1.
RESTRICTED= variables that were predicated on former U.S. export
regulations. Add CRYPTO=, as necessary, so it's still possible to
exclude all crypto packages from a build by setting MKCRYPTO=no
(but "lintpkgsrc -R" will no longer catch them).
Specifically,
- - All packages which set USE_SSL just lose their RESTRICTED
variable, since MKCRYPTO responds to USE_SSL directly.
- - realplayer7 and ns-flash keep their RESTRICTED, which is based
on license terms, but also gain the CRYPTO variable.
- - srp-client is now marked broken, since the distfile is evidently
no longer available. On this, we're no worse off than before.
[We haven't been mirroring the distfile, or testing the build!]
- - isakmpd gets CRYPTO for RESTRICTED, but remains broken.
- - crack loses all restrictions, as it does not evidently empower
a user to utilize strong encryption (working definition: ability
to encode a message that requires a secret key plus big number
arithmetic to decode).
Add a new USE_LIBTOOL definition that uses the libtool package instead of
pkglibtool which is now considered outdated.
USE_PKGLIBTOOL is available for backwards compatibility with old packages
but is deprecated for new packages.
changes include some bugfixes, a new BSD-like license, as well as
support for archives with more than 2^16-1 files.
Zlib support still broken, so we use the one coming with the distribution.
Changes include:
* Updated the configure system to use Autoconf 2.13, Automake 1.4 and
Libtool 1.3.3.
* enhanced example programs a little bit
* no changes to the compression code - LZO has proven to be stable
- fetch the shar file so we don't need tar
- do not install info files (they will be a separate pkg), as we need
tar to unpack the gtexinfo distribution
- on Solaris we get .mo files instead of .cat files (I'm guessing for
Linux, please someone verify and adjust Makefile appropriately)
rewritten. Allows for USA/non-USA support via the familiar USE_RSAREF2
mechanism, and significantly cleaned up. Does not attempt to fall back to
$HOME/.pgp for keys as in the FreeBSD port, as other programs already
require PGPPATH to be set.
In the vast majority of cases, nothing has changed (i.e. .tgz, .tar.gz,
and .tar.bz2).
EXTRACT_USING_PAX can be set as before.
For custom extractions, instead of using EXTRACT_BEFORE_ARGS,
EXTRACT_AFTER_ARGS and EXTRACT_CMD, simply set EXTRACT_CMD to be the
command needed to decompress and extract the lements from the archive.
${DOWNLOADED_DISTFILE} can be used to reference the distfile(s).
e.g. for compressed shars, where previously there was:
EXTRACT_CMD= ${GZCAT}
EXTRACT_BEFORE_ARGS=
EXTRACT_AFTER_ARGS= |sh
now use:
EXTRACT_CMD= ${GZCAT} ${DOWNLOADED_DISTFILE} | ${SH}
(The latest binutils-based strip can do this if you tell it which
obj-format the binary is, but 1.3.x doesn't support this. Plus, that
BSDi(?)-binary is stripped anyways.)
