changes:
-disable aalib by default
-"--list-all-config" to dump the full config tree + values
-bugfixes
-translation updates
pkgsrc note: dropped aalib support
alternative from mk/jpeg.buildlink3.mk
This allows selection of an alternative jpeg library (namely the x86 MMX,
SSE, SSE2 accelerated libjpeg-turbo) via JPEG_DEFAULT=libjpeg-turbo, and
follows the current standard model for alternatives (fam, motif, fuse etc).
The mechanical edits were applied via the following script:
#!/bin/sh
for d in */*; do
[ -d "$d" ] || continue
for i in "$d/"Makefile* "$d/"*.mk; do
case "$i" in *.orig|*"*"*) continue;; esac
out="$d/x"
sed -e 's;graphics/jpeg/buildlink3\.mk;mk/jpeg.buildlink3.mk;g' \
-e 's;BUILDLINK_PREFIX\.jpeg;JPEGBASE;g' \
< "$i" > "$out"
if cmp -s "$i" "$out"; then
rm -f "$out"
else
echo "Edited $i"
mv -f "$i" "$i.orig" && mv "$out" "$i"
fi
done
done
gphoto2 2.4.2
* Updated translations.
* Major change in behaviour:
--capture-image split into:
--capture-image : Just captures image, no download.
--capture-image-and-download : captures image and downloads it.
gphoto2 2.4.1
* Made capture preview that saves to files work
* capture-image has no arguments
* version check for libgphoto2 fixed
* cs,da,it,vi translations updated
gphoto2 2.4.0
* Add contrib/ directory with scripts and things contributed by users.
* New --storage-info function to get direct storage information from the
camera via API.
* Use SIGUSR1 to trigger premature image capture in --interval mode.
* New --reset-interval parameter makes SIGUSR1 reset the capture
interval.
* New --capture-tethered command to wait for presses of the camera
shutter button and download. Confirmed working only with Nikon DSC.
* Added --hook-script option, including man page update and test-hook.sh.
* Fix: --get-all-metadata takes no argument.
Changes 2.3.0:
* Require popt library to parse command line options.
* Partitioned command line options into groups of related options.
* Added --debug-logfile=FILENAME option.
* Only load all camlibs if necessary.
* (Half-)Fix to make --with-libgphoto2=PREFIX configure parameter work.
* Preliminary support for lower-case filenames in --filename pattern: %:
* Added "rmdir" command to gphoto2 --shell.
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.
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.
file's sole purpose was to provide a dependency on pkg-config and set
some environment variables. Instead, turn pkg-config into a "tool"
in the tools framework, where the pkg-config wrapper automatically
adds PKG_CONFIG_LIBDIR to the environment before invoking the real
pkg-config.
For all package Makefiles that included pkg-config/buildlink3.mk, remove
that inclusion and replace it with USE_TOOLS+=pkg-config.
changes:
- New command line arguments:
--list-config - dump the configuration tree of the camera
--get-config var - get the configuration entry <var>
- New capture option:
--frames=count
--interval=seconds
-fixes
-new translations
"BUILDLINK_DEPENDS.libexif" because the package no longer works with old
version of the "libexif" packacke. Bump package revision because of
these changes.
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.
curses.buildlink2.mk. This was wrong because we _really_ do want to
express that we want _n_curses when we include the buildlink2.mk file.
We should have a better way to say that the NetBSD curses doesn't
quite work well enough. In fact, it's far better to depend on ncurses
by default, and exceptionally note when it's okay to use NetBSD curses
for specific packages. We will look into this again in the future.