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=...").
Pkgsrc changes:
o Canonicalize the HOMEPAGE on search.cpan.org.
Upstream changes:
1.04 Wed Jul 04 20:00:00 2007
- Fixed line 229 to avoid unit value warnings.
- Updated old-style &function calls.
- Fixed conflicts between global our $DEBUG and
function-internal my $DEBUG.
- General formatting stuff (whitespace, single vs. double
quotes, etc.)
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.
Collection. I had that one sitting here for a few months... I don't even
remember writing it, so maybe proper credit is lacking. In such case tell
me so.
The Term-Prompt module can be used to accept interactive input. You specify
the type of inputs allowed, a prompt, help text and defaults and it will deal
with the user interface, (and the user!), by displaying the prompt, showing the
default, and checking to be sure that the response is one of the legal choices.
Additional "types" that could be added would be a phone type, a social security
type, a generic numeric pattern type...
