1) Linking a shared library against a static "socks{4,5}" library
does not have the desired effect of eliminating the dependency on
"socks" (not as it does for binaries).
2) No package linked against "libwww" seems to actually utilize
"socks".
Also bump the PKGREVISION and buildlink DEPENDS to the current level,
and liberalize the (formal) dependency on "openssl", for the benefit
of pre-NetBSD-1.5 systems. From now on, we can have no more issues
with "openssl" or "socks{4,5}" versions, as only the libwwwssl.*
shared libraries carry a run-time dependency on "openssl", but no
package links against them, and no "libwww" shared libraries can carry
a run-time dependency on any "socks" libraries. [Previous versions, of
course, may have had issues -- see PR 17010, which this is a partial
fix for.]
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.
Include a bugfix for lisp_LISP independently discovered by me that has
been pulled up to the automake-1-4 branch of automake cvs.
Changes are:
New in 1.4-p5:
* Allow AM_PROG_LIBTOOL again.
* Diagnose AC_CONFIG_HEADERS the same as AC_CONFIG_HEADER.
* Display distributed file list correctly in usage message.
* Allow numbers in macro names.
* Bugfixes.
New in 1.4-p4:
* Deal with configure.ac as well as configure.in -- this time for real!
* The version numbering system now allows three point version numbers,
such as 1.4.4, without thinking they are alpha release numbers.
New in 1.4-p3:
* Deal with configure.ac as well as configure.in.
* Don't complain if `version.texi' is included in multiple places.
New in 1.4-p2:
* Deal with AC_CONFIG_FILES from autoconf-2.50.
* Improvements to f77 support.
* DESTDIR now works for script targets.
* distcheck-hook works correctly.
New in 1.4-p1:
* The version numbering system now allows fork identifiers (such as
the p1 in this version of automake).
* Cope gracefully with various versions of libtool which may or may not
require ltconfig, ltcf-c.sh, ltcf-cxx.sh or ltcf-gcj.sh.
* Bugfixes.
set FOO_CONFIG=${BUILDLINK_CONFIG_WRAPPER.foo} in both CONFIGURE_ENV and
MAKE_ENV. We remove the check for GNU_CONFIGURE because if a package
Makefile includes the buildlink.mk file, then it most likely wants to use
the config script wrappers as well. Change suggested by Hubert Feyrer
(hubertf) and Tomasz Luchowski (zuntum).
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>.
baggage for packages that have ${DEPENDS} on the libwww package, but
don't need to link in "libwwwssl" (currently all of them). These
packages _do_ _not_ need to have their DEPENDS changed now, as the
package system currently makes them require "libssl", whether they
truly require it to run, or not.
This will prove useful, however, when the version number of the
"libssl.so" shared library is bumped[1]. Then, we'll have to bump
again, but the depending packages will only need to depend on _this_
version, "libwww>=5.3.2nb1", the first version in which the "libwww*"
libraries (except libwwwssl) carry no dependency on "libssl".
[1] It's already been bumped in the HEAD of the base tree, but not
yet in the openssl package or in any release branch.
on other libraries, on both ELF and (NetBSD/)a.out, to make
libwwwssl.so.?.? depend on the correct openssl shared libraries, as
determined by the setting of ${SSLBASE} in bsd.pkg.mk. This closes PR
pkg/12570, and has the additional advantage that programs that _do_ _not_
need to link in "-lwwwssl" won't get "-lssl" or "-lcrypto" at all.
Also, make"w3c" and "www" build again with USE_SOCKS=4.
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>
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.
grautiutiously reinstalled whenever "perl" is reinstalled. For the
NetBSD package, the dependence on autoconf and automake has already
been removed, so it remained only to patch the configure script.
This is a minor release that mainly provides bug fixes and small
enhancements that have been commited to CVS since the last release.
Vladimir Koslov provided indispensable help for testing and preparing the
Win32 release. Special thanks to Wayne Davison, Art Barstow, Peter
Stamfest, Zhu Qun-Ying, Jens Meggers, Ken Olum for their contributions.
* Summary of principal changes (the ChangeLog provides a detailed account)
+ The following sample applications could core dump
under Windows: head.c, getheaders.c, chunk.c, chunkbody.c,
multichunk.c
+ When retrieving an object from the cache, the HTTP headers
associated with the object weren't stored in the HTResponse object.
+ The cache garbage collector could go into an endless loop.
+ The HTResponse object now returns the HTTP reason.
+ Update of expat to version 19990728.
+ Optimization, enhancements, and bugs fixes to the HTRDF module
+ Some memory leaks and compiler warning fixes.
+ The robot could hang when accessing local files.
+ Optimization of the HTChunk and HTHash modules.
* Outstanding bugs
+ The webbot crashes from time to time under Windows. It
seems to be a problem while reading the robots.txt file,
there the application frees a request that's still registred
in the Windows async. loop.,
+ The tiny.c sample application doesn't prompt the user with
a text input.
+ Interpretation of FD_CLOSE under Windows.
+ The FTP implementation has memory leaks and doesn't
remember the path or authentication information correctly.
+ Compiling with -O2 and -Wall reveals some unitialized
variables in HTDIR and HTFTP.
* To do
+ Compile the answers to the libwww survey (volunteers are welcome).
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).
many bug fixes -- too many to list, full release history online at
<http://www.w3.org/Library/User/ReleaseNotes.html> -- and a few new features.
The most significant is integrated libwww-SSL. Also SOCKS "punching through
firewalls" support is present now (but untested by me). Not sure when that
appeared, exactly.
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.
assumes the user is defining his own HText stuff. If they aren't, as
often is the case with the shared lib use.. Then it breaks horribly.
Welcome to the wonderful world of "ld resolves all external references
at link time"
- New, optional Makefile variable HOMEPAGE, specifies a URL for
the home page of the software if it has one.
- The value of HOMEPAGE is used to add a link from the
README.html files.
- pkglint updated to know about it. The "correct" location for
HOMEPAGE in the Makefile is after MAINTAINER, in that same
section.
