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.
per maintainer update request by PR 46541.
ChangeLog:
- 0.22 ... Add DIST and MANIF config options.
- 0.19 ... If EXPORT_TAGS_ALL is set, then it's now unnecessary
to set EXPORT_OK_ALL
- 0.18 ... Add CPPFLAGSEX, BOOT_F and PRE_HEAD config options.
Add script.in (which generates the c2xs script)
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!
InlineX::C2XS - create an XS file from an Inline C file.
The C file that InlineX::C2XS needs to find would contain
only the C code.
InlineX::C2XS looks for the file in ./src directory,
expecting that the filename will be the same as what
appears after the final '::' in the module name (with a
'.c' extension).ie if the module is calle My::Next::Mod
it looks for a file ./src/Mod.c, and creates a file
named Mod.xs. Also created, is the file 'INLINE.h' - but
only if that file is needed. The generated xs file (and
INLINE.h) will be written to the cwd unless a third argument
(specifying a valid directory) is provided to the c2xs()
function.
The created XS file, when packaged with the '.pm' file, an
appropriate 'Makefile.PL', and 'INLINE.h' (if it's needed),
can be used to build the module in the usual way - without
any dependence upon the Inline::C module
