a934b7d636
Tarsnap 1.0.38 is now available. This version brings several new features compared to tarsnap 1.0.37: * Tarsnap now supports OpenSSL 1.1. * tarsnap accepts an --iso-dates option, which causes times to be printed in YYYY-MM-DD HH:MM:SS format rather than the traditional unix "ls -l" style. * tarsnap accepts a --force-resources option to proceed with decryption of a passphrase-encrypted key file even if it is anticipated to use an excessive amount of memory or CPU time. (This may be useful if tarsnap inaccurately estimates the amount of memory your system has available.) * tarsnap accepts an --archive-names <file> option, which reads a list of archive names to operate on when operating in -d and --print-stats modes. (This should make some scripts simpler; no more need to construct a command line which has '-f' inserted before each archive name.) Potentially (but unlikely) breaking changes in this code compared to tarsnap 1.0.37: * tarsnap now applies the --humanize-numbers option to the "progress" output printed by SIGINFO / SIGUSR1. If you have scripts which send signals to tarsnap and parse its output, they may need to be updated. * tarsnap -v now prints 'Deleting archive "foo"' even if only one archive is being deleted. If you have scripts which parse the output of tarsnap -v, they may need to be updated. * tarsnap now prints a warning if you pass '--configfile /nosuchfile'. If you have scripts which rely on being able to specify nonexistent configuration files and not get any warnings from tarsnap, they may need to be updated. (Also, if you were doing that, I *really* want to know why.) There are also two changes which most users should not encounter: * tarsnap now has an --initialize-cachedir mode; this is intended for use by the GUI. (The cache directory will be initialized automatically in normal usage of the tarsnap command-line utility.) * tarsnap's configure script takes a --with-conf-no-sample option which results in the sample tarsnap configuration file being installed as "tarsnap.conf" rather than "tarsnap.conf.sample". This is intended for use in some packaging systems which have mechanisms for managing configuration files, and should probably not be used by hand (since it will overwrite your existing tarsnap.conf).
21 lines
673 B
Makefile
21 lines
673 B
Makefile
# $NetBSD: Makefile,v 1.14 2017/07/15 06:11:56 wiz Exp $
|
|
|
|
DISTNAME= tarsnap-autoconf-1.0.38
|
|
PKGNAME= ${DISTNAME:S/-autoconf//}
|
|
CATEGORIES= sysutils archivers security
|
|
MASTER_SITES= https://www.tarsnap.com/download/
|
|
EXTRACT_SUFX= .tgz
|
|
|
|
MAINTAINER= pkgsrc-users@NetBSD.org
|
|
HOMEPAGE= https://www.tarsnap.com/
|
|
COMMENT= Secure online backup service
|
|
LICENSE= tarsnap-license
|
|
|
|
GNU_CONFIGURE= yes
|
|
INSTALL_MAKE_FLAGS= sysconfdir=${PREFIX}/share/examples/tarsnap
|
|
|
|
CONF_FILES= ${PREFIX}/share/examples/tarsnap/tarsnap.conf.sample ${PKG_SYSCONFDIR}/tarsnap.conf
|
|
|
|
.include "../../security/openssl/buildlink3.mk"
|
|
.include "../../devel/zlib/buildlink3.mk"
|
|
.include "../../mk/bsd.pkg.mk"
|