{perl>=5.16.6,p5-ExtUtils-ParseXS>=3.15}:../../devel/p5-ExtUtils-ParseXS
since pkgsrc enforces the newest perl version anyway, so they
should always pick perl, but sometimes (pkg_add) don't due to the
design of the {,} syntax.
No effective change for the above reason.
Ok joerg
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.
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.
to trigger/signal a rebuild for the transition 5.10.1 -> 5.12.1.
The list of packages is computed by finding all packages which end
up having either of PERL5_USE_PACKLIST, BUILDLINK_API_DEPENDS.perl,
or PERL5_PACKLIST defined in their make setup (tested via
"make show-vars VARNAMES=..."), minus the packages updated after
the perl package update.
sno@ was right after all, obache@ kindly asked and he@ led the
way. Thanks!
to trigger/signal a rebuild for the transition 5.8.8 -> 5.10.0.
The list of packages is computed by finding all packages which end
up having either of PERL5_USE_PACKLIST, BUILDLINK_API_DEPENDS.perl,
or PERL5_PACKLIST defined in their make setup (tested via
"make show-vars VARNAMES=...").
Mail::Sender's one problem is its a bit cumbersome to use, with so
many options and things to open, close, the whole thing, parts,
multiparts etc etc., and several ways to check for successs. Its
hard to remember what needs done at what point with what data to
do what you want and then which way you check what data based on
what was done to see if it worked or not.
This module's aim is to make all of that ``Easy''
It does so by providing a single function (and method) to send mail
based on an (IMHO) easier to work with hashref and returns true or
false on success or failer and sets $@ to any errors.
The EXAMPLE section shows an ``email or die'' that will send an
email using SMTP Auth on port 26 with text and html parts, the html
part has a smiley gif embedded inline and a PDF attached and a high
priority flag and read and delivery receipt requests. It will take
you seconds to customize it to send that to yourself (and its
``Easy'' to understand what its going on without having to understand
the intracacies of SMTP and MIME messages.
