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=...").
Pkgsrc changes:
- Changed HOMEPAGE because of new maintainer.
- PACKLIST changed because the name of the _module_ is now IO::Stringy.
Changes since version 2.109:
============================
* 2208 IO::ScalarArray->getline does not return undef for EOF if
undef($/)
* 7132 IO-stringy/Makefile.PL bug - name should be module name
* 11249 IO::Scalar flush shouldn't return undef
* 2172 $\ (output record separator) not respected
* 8605 IO::InnerFile::seek() should return 1 on success
* 4798 *.html in lib/
* 4369 Improvement: handling of fixed-size reads in IO::Scalar
(Actually, bug 4369 was closed in Version 2.109)
developer is officially maintaining the package.
The rationale for changing this from "tech-pkg" to "pkgsrc-users" is
that it implies that any user can try to maintain the package (by
submitting patches to the mailing list). Since the folks most likely
to care about the package are the folks that want to use it or are
already using it, this would leverage the energy of users who aren't
developers.
module directory has changed (eg. "darwin-2level" vs.
"darwin-thread-multi-2level").
binary packages of perl modules need to be distinguishable between
being built against threaded perl and unthreaded perl, so bump the
PKGREVISION of all perl module packages and introduce
BUILDLINK_RECOMMENDED for perl as perl>=5.8.5nb5 so the correct
dependencies are registered and the binary packages are distinct.
addresses PR pkg/28619 from H. Todd Fujinaka.
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.
Added untested SEEK, TELL, and EOF methods to IO::Scalar and
IO::ScalarArray to support corresponding functions for tied
filehandles
Removed not-fully-blank lines from modules; these were causing lots
of POD-related warnings
IO::Scalar objects can now be made sensitive to $/ . Pains were
taken to keep the fast code fast while adding this feature
IO::Scalar has a new sysseek() method
* Added 'bool' overload to '""' overload, so object always evaluates
to true.
* Evaluating an IO::Scalar in a string context now yields the
underlying string. *Thanks to B. K. Oxley (binkley) for this.*
* Minor documentation fixes.
ones to do, and each compiled and installed/de-installed apparently
correctly.
As a side effect of the dynamic PLIST, we no longer need to have separate
-static and -shared PLISTs. It's now easier than ever to make a perl5
package for NetBSD :)
