Commit graph

5 commits

Author SHA1 Message Date
jlam
cc4128d97e Buildlinkify, in the sense that only the perl headers are found in
${PREFIX} -- everything else is pickup up from ${BUILDLINK_DIR}.
2001-11-26 06:49:36 +00:00
zuntum
c72c1cf5f9 Move pkg/ files into package's toplevel directory 2001-11-01 00:57:41 +00:00
veego
63ad910dee SVR4 packages have a limit of 9 chars for a package name.
The automatic truncation in gensolpkg doesn't work for packages which
have the same package name for the first 5-6 chars.
e.g. amanda-server and amanda-client would be named amanda and amanda.
Now, we add a SVR4_PKGNAME and use amacl for amanda-client and amase for
amanda-server.
All svr4 packages also have a vendor tag, so we have to reserve some chars
for this tag, which is normaly 3 or 4 chars. Thats why we can only use 6
or 5 chars for SVR4_PKGNAME. I used 5 for all the packages, to give the
vendor tag enough room.
All p5-* packages and a few other packages have now a SVR4_PKGNAME.
2001-10-18 15:20:01 +00:00
jlam
0cec9f63e0 Change foo-* dependencies into foo-[0-9]* dependencies so we match only
those packages with a base package name of "foo".
2001-09-27 07:36:12 +00:00
jlam
08f677a980 p5-Mail-ListDetector - perl5 module to detect whether a message is from a
mailing list

This module analyzses Mail::Internet objects. It returns a
Mail::ListDetector::List object representing the mailing list.

The RFC2369 mailing list detector is also capable of matching some
Mailman and Ezmlm messages. It is deliberately checked last to allow
the more specific Mailman and Ezmlm parsing to happen first, and more
accurately identify the type of mailing list involved.

Provided in pkg/13847 by Sen Nagata <sen@eccosys.com>.
2001-09-27 04:57:45 +00:00