CVS log for pkgsrc/sysutils/safetynet/Makefile

Up to [cvs.NetBSD.org] / pkgsrc / sysutils / safetynet

Request diff between arbitrary revisions

Keyword substitution: kv
Default branch: MAIN

*: recursive bump for perl 5.36

*: recursive bump for perl 5.34

*: bump PKGREVISION for perl-5.32.

Bump PKGREVISIONs for perl 5.30.0

Recursive bump for perl5-5.28.0

Bump PKGREVISION for perl-5.24.0 for everything mentioning perl.

Recursive PKGREVISION bump for all packages mentioning 'perl',
having a PKGNAME of p5-*, or depending such a package,
for perl-5.22.0.

Bump for perl-5.20.0.
Do it for all packages that
* mention perl, or
* have a directory name starting with p5-*, or
* depend on a package starting with p5-
like last time, for 5.18, where this didn't lead to complaints.
Let me know if you have any this time.

Bump all packages for perl-5.18, that
a) refer 'perl' in their Makefile, or
b) have a directory name of p5-*, or
c) have any dependency on any p5-* package

Like last time, where this caused no complaints.

Drop superfluous PKG_DESTDIR_SUPPORT, "user-destdir" is default these days.

Bump all packages that use perl, or depend on a p5-* package, or
are called p5-*.

I hope that's all of them.

service suspended. prevent timeout. fetch from backup.

Reset maintainer for developers who gave back their commit bit.

DESTDIR support

Get rid of USE_PERL5.  The new way to express needing the Perl executable
around at either build-time or at run-time is:

	USE_TOOLS+=	perl		# build-time
	USE_TOOLS+=	perl:run	# run-time

Also remove some places where perl5/buildlink3.mk was being included
by a package Makefile, but all that the package wanted was the Perl
executable.

Create directories before installing files into them.

Move WRKSRC definition away from the first paragraph in a Makefile.

COMMENT should start with a capital letter.

s/netbsd.org/NetBSD.org/

Place WRKSRC where it belongs, to make pkglint happy; ok'ed by wiz.

Initial import of safetynet-1.15

safetynet allows you to monitor and restart processes without having to
write large and complicated init scripts. The config file is easy to
understand and learn and you can have the whole script setup and running
in under 10m, so you can get on with doing more important things than
worrying if your ssh daemon is still running.

Initial revision