Commit graph

16 commits

Author SHA1 Message Date
joerg
76039544d1 Remove @dirrm related logic. 2009-06-14 22:57:58 +00:00
jlam
a80fd13efc Mechanical changes to add DESTDIR support to packages that install
their files via a custom do-install target.
2008-03-04 17:57:17 +00:00
joerg
cdd2a75801 Fix path to Perl and Bash, bump revision. The bash script might either
be a normal Bourne script or easily fixable, but leave that to the
maintainer.
2007-09-04 20:54:29 +00:00
rillig
2829e658f2 Mechanically replaced man/* with ${PKGMANDIR}/* in the definition of
INSTALLATION_DIRS, as well as all occurrences of ${PREFIX}/man with
${PREFIX}/${PKGMANDIR}.

Fixes PR 35265, although I did not use the patch provided therein.
2007-01-07 09:13:46 +00:00
rillig
3889702421 Fixed those pkglint warnings that concern the SUBST blocks. 2006-07-04 09:13:49 +00:00
joerg
5911def816 Recursive revision bump / recommended bump for gettext ABI change. 2006-02-05 23:08:03 +00:00
jlam
dc9594e09d Remove USE_PKGINSTALL from pkgsrc now that mk/install/pkginstall.mk
automatically detects whether we want the pkginstall machinery to be
used by the package Makefile.
2005-12-29 06:21:30 +00:00
rillig
b71a1d488b Fixed pkglint warnings. The warnings are mostly quoting issues, for
example MAKE_ENV+=FOO=${BAR} is changed to MAKE_ENV+=FOO=${BAR:Q}. Some
other changes are outlined in

    http://mail-index.netbsd.org/tech-pkg/2005/12/02/0034.html
2005-12-05 20:49:47 +00:00
jlam
3e474a90d8 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.
2005-07-16 01:19:06 +00:00
jlam
81edaaa606 Create directories before installing files into them. 2005-06-16 06:57:37 +00:00
reed
ee8be9d0c1 RCD_SCRIPTS_EXAMPLEDIR is no longer customizable.
And always is defined as share/examples/rc.d
which was the default before.

This rc.d scripts are not automatically added to PLISTs now also.
So add to each corresponding PLIST as required.

This was discussed on tech-pkg in late January and late April.

Todo: remove the RCD_SCRIPTS_EXAMPLEDIR uses in MESSAGES and elsewhere
and remove the RCD_SCRIPTS_EXAMPLEDIR itself.
2005-05-02 20:33:57 +00:00
agc
8758983939 Add RMD160 digests. 2005-02-24 09:59:20 +00:00
reed
32d8f290c2 The default location of the pkgsrc-installed rc.d scripts is now
under share/examples/rc.d. The variable name already was named
RCD_SCRIPTS_EXAMPLEDIR.

This is from ideas from Greg Woods and others.

Also bumped PKGREVISION for all packages using RCD_SCRIPTS mechanism
(as requested by wiz).
2004-12-28 02:47:40 +00:00
agc
d213816536 Use the correct path for p5-Convert-BinHex. 2004-09-26 18:35:51 +00:00
grant
f90c09f233 make it clear that this pkg doesn't depend on packages, but leaves it to
the administrator to install optional packages that mailscanner can
make use of.
2004-09-25 04:18:06 +00:00
grant
e2fbe90aa7 Initial import of mailscanner-4.30.3.2 into the NetBSD packages collection.
MailScanner is a complete e-mail security system designed for use on
e-mail gateways. It protects against viruses, and detects attacks against
e-mail client packages (such as Outlook, Outlook Express, Eudora). It
can also detect almost all unsolicited commercial e-mail (spam) passing
through it and respond to all incidents in a wide variety of ways.

Not only can it scan for known viruses, but it can also protect against
unknown viruses hidden inside e-mail attachments by refusing entry to
attachments whose filenames match any given pattern. This can include
generic patterns that trap filenames attempting to hide the true filename
extension (e.g. ".txt.vbs").

It is superior to many commercial packages in its ability to handle
attacks against itself, such as Denial Of Service attacks caused by
messages containing the "Zip of Death". It is easy to install into an
existing e-mail gateway, requiring very little knowledge of sendmail
and no change to an existing sendmail configuration.

MailScanner itself is entirely open source, but it uses widely known
commercial virus scanning packages at its core. The other software it
uses is all high quality open source software, leading to a system that
can be trusted for performance and reliability.
2004-09-25 00:33:19 +00:00