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=...").
1.04 Mon 24 Mar 2008
- Removing dependency on File::Slurp
1.03 Sat 1 Mar 2008
- Incremental release to clear out some CPAN Testers failures
- No need to upgrade
1.02 Tue 11 Dec 2007
- Cygwin is clearly insane, skip root and win32 test sets
- More aggressive dependencies, particularly on Win32
1.01 Tue 11 Dec 2007
- No functional changes
- Correcting dependency
- Updating to Module::Install 0.68
- Updating bundled tests
Based on patch provided by Martin Wilke via PR 34348.
And since this version, no need to build depend on p5-ExtUtils-AutoInstall.
Changes:
0.96 Wed 19 Jul 2006
- Moving from CVS to new SVN repository
- Upgrading to Module::Install
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.
File::Flat implements a flat file system. A flat file system is a
file system in which directories do not exist. It provides an
abstraction over any normal file system which makes it appear as if
directories do not exist. In effect, it will automatically create
directories as needed. This is create for things like install
scripts and such, as you never need to worry about the existence
of directories, just write to a file, no matter where it is.
