had actually been ignoring LTCONFIG_OVERRIDE anyway and just using
the default LIBTOOL_OVERRIDE to replace libtool scripts in packages.
This just formalizes the fact that LTCONFIG_OVERRIDE is not used
meaningfully by pkgsrc.
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".
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".]
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.
* Canon PowerShot library reverse-engineered by
Wolfgang Reissnegger
Werner Almesberger <almesber@lrc.di.epfl.ch>
Rasmus Andersen <rasmus@diku.dk>
Edouard Lafargue <lafargue@oslo.geco-prakla.slb.com>
Philippe Marzouk <bullmali@afribone.net.ml>
Ole W. Saastad <o.w.saastad@kjemi.uio.no>
* New Kodak DC21x library and standalone dc21x_cam by Timecop <timecop@japan.co.jp>
* Sony DSCF55/505/MSAC-SR1/DCR-PC100 library enhancements.
* Support for Sony MSAC-SR1 and Memory Stick used by DCR-PC100.
* Standalone rsony program by Mark Davies <mdavies@dial.pipex.com>
* New patches contributed by Kees Cook <cook@cpoint.net>, Juergen Weigert <jw@netvision.de>, and
Bernd Seemann <bernd@seebaer@ruhr.de> for downloading MPEGs with the standalone program.
* Additional Fuji camera models have been comfirmed to work.
* Konica and HP library fixes by by Ed Legowski <edlegowski@pobox.com>.
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.
New patches for FreeBSD, OpenBSD, and NetBSD, Sony DSC F55 library changes,
a Canon A50 library and general fixes, Canon A5 compatibility fixes, Sony
DSC F505 and Sony memory stick adapter support, an HTML Gallery path fix,
and a GNOME desktop entry.
gPhoto is an universal, free GTK+ application that will allow
downloading, saving, and manipulation of images from several
different digital camera models, or from the local harddrive.
gPhoto has a basic command line interface, which is handy,
if you want to set up a web camera, and use gphoto in a
script, e.g. with Perl/PHP.
gPhoto sports a new HTML engine, that let's you create your
gallery "themes" (HTML with special tags), and publish images
to the web. A directory browse mode has also been implemented.
gPhoto supports a wide array of digital camera models.