Re: [Module-build-general] [comments please] module installation paths

[Dave R. <au...@ur...>]

On Mon, 30 Jun 2003, Uri Guttman wrote:

>   KW> =item bin
>
>   KW> "Architecture-dependent" programs, i.e. compiled C code or something.
>   KW> Pretty rare to see this in a perl distribution, but it happens.
>
> xs (or now inline::) code isn't that rare. i would drop the last
> line. you could make a comment about these programs use XS or
> inline::c/cpp or other cpu architecture dependent stuff. also what
> compiler will be chosen for that? i didn't see any override options in
> this doc.

He means that compiling binary _executable_ is a rarity in Perl module
distros, as opposed to compiled modules.

>   KW> =item bindoc
>
>   KW> Documentation for the stuff in C<script> and C<bin>.  Usually
>   KW> generated from the POD in those files.  Under Unix, these are manual
>   KW> pages belonging to the 'man1' category.
>
> can the pod be generated from another command? stem will have a stem2pod
> command that needs to be run since some of the pod is autogenerated from
> attribute specifications.

Module::Build is very flexible, so doing extra stuff is always possible at
each stage of the build/test/install process (as well as during distro
generation, etc.)


-dave

/*=======================
House Absolute Consulting
www.houseabsolute.com
=======================*/