how to stop module::build from building html docs

[Anonymous Monk]

thanks in advance

[moritz]

My Module::Build setups don't build HTML docs. So the answer is probably "don't do whatever you're doing wrong".

See also How (Not) To Ask A Question.

[syphilis]

don't do whatever you're doing wrong

Heh ... not so sure that's a very helpful response, moritz. Whenever I build with Module::Build, html docs *do* get created ... and I have no idea what controls this behaviour. Of course, I don't personally care all that much, but I think the op's question is a reasonable one.

Cheers,
Rob

[moritz]

Heh ... not so sure that's a very helpful response

So how do you expect me to help our anonmonk when he doesn't provide some code that reproduce the problem? Which is why I kindly directed him/her to How (Not) To Ask A Question.

I tested it with a fairly simple Build.PL file, and neither ./Build nor ./Build dist generated any HTML. (Tested with the M::B shipped with perl-5.10.0)

Shouldn't it be the other way round, that people who observe undesirable behaviour (and want to get rid of it) tell those who might help how to reproduce it?

Instead of telling me how unhelpful my response was, could you please tell me how to reproduce the OP's problem?

[rhesa]

I haven't tested this, but I think this is a feature that's configured when you *build* perl.

From the Module::Build documentation:

html

[version 0.26]

This will generate HTML documentation for any binary or library files under blib/ that contain POD. The HTML documentation will only be installed if the install paths can be determined from values in "Config.pm". You can also supply or override install paths on the command line by specifying "install_path" values for the "binhtml" and/or "libhtml" installation targets.

I don't have those paths in my Config.pm, and Module::Build doesn't generate html docs. If you want to turn it off forever, editing Config.pm is probably the quickest and surest way.

Otherwise, have a look at the installdirs and install_paths command line options. Something like

perl Build.PL --install_path binhtml= --install_path libhtml=

might just suppress generating html.

[Anonymous Monk]

Sadly perl Build.PL --install_path binhtml= --install_path libhtml= didn't work. Thanks

[Intrepid]

I've run into this problem myself

Updated: 2013-01-30 Eastern Standard Time
Reason: reply by Anonymous monk

I have no acceptable* solution for preventing Module::Build from building Html from POD in the distribution. I have found, however, a way to prevent it from installing Html files when I issue the ./Build install command.

Reported based on installed Module::Build v0.38

Read more... (3 kB)

Update:

I'll show the results of trying some other things. Note that there is a null solution here. These flags still do not work.

Building Module-Runtime

$ perl Build.PL
Checking whether your kit is complete...
Looks good

Checking prerequisites...
Looks good

Deleting MYMETA.yml
Removed previous 'MYMETA.yml'
Deleting MYMETA.json
Removed previous 'MYMETA.json'
Created MYMETA.yml and MYMETA.json
Deleting Build
Removed previous script 'Build'
Creating new 'Build' script for 'Module-Runtime' version '0.013'

$ ./Build fakeinstall
Building Module-Runtime
Copying lib/Module/Runtime.pm -> blib/lib/Module/Runtime.pm
Manifying blib/lib/Module/Runtime.pm -> blib/libdoc/Module.Runtime.3pm
Converting Pod to HTML with Pod::Html 1.11
HTMLifying blib/lib/Module/Runtime.pm -> blib/libhtml/site/lib/Module/
+Runtime.html
P::H::pod2html --flush --title=Module::Runtime - runtime module handli
+ng --podpath=lib/perl5/5.14:bin:lib/perl5/site_perl/5.14 --infile=bli
+b/lib/Module/Runtime.pm --outfile=blib/libhtml/site/lib/Module/Runtim
+e.tmp --podroot=/usr --htmlroot=../../.. --header --backlink=Back to 
+Top
Installing /usr/local/lib/perl5/Module/Runtime.pm
Installing /usr/local/share/man/man3perl/Module.Runtime.3pm
Installing /usr/local/html/site/lib/Module/Runtime.html
Writing /usr/local/lib/perl5/cygwin-thread-multi-64int/auto/Module/Run
+time/.packlist

$ printenv PERL_MB_OPT
--verbose --install_base=/usr/local --install_path bindoc=/usr/local/s
+hare/man/man1 --install_path libdoc=/usr/local/share/man/man3perl --c
+onfig installhtmldir= --config installhtml1dir= installhtml3dir= --co
+nfig installsitehtml1dir= installsitehtml3dir=
$ exit

Notice the output line:
Installing /usr/local/html/site/lib/Module/Runtime.html

---

* Editing Config.pm is considerably unacceptable where a package manager is managing the perl installation (by upgrading with files created by a package-creation worker somewhere far, far away). As is the case for the vast majority of users of Perl ( /machines where perl is installed/ ) now.

[Anonymous Monk]

See How to stop Module::Build from generating html?

perl Build.PL --config installhtml1dir= installhtml3dir= installman1dir= installman3dir= installsitehtml1dir= installsitehtml3dir= installsiteman1dir= installsiteman3dir= installvendorhtml1dir= installvendorhtml3dir= installvendorman1dir= installvendorman3dir=

perl Build.PL --config installhtmldir=

perl -e " $ENV{PERL_MB_OPT}=q{ --config installhtml1dir= installhtml3dir= installman1dir= installman3dir= installsitehtml1dir= installsitehtml3dir= installsiteman1dir= installsiteman3dir= installvendorhtml1dir= installvendorhtml3dir= installvendorman1dir= installvendorman3dir= }; exec $^X, q{Build.PL}; "

CPANPLUS#buildflags

untested perl -MConfig_m Build.PL

[apl]

Please don't replace your original question with a 'Thanks'. It confuses the rest of us who can only see the answers to a non-existent question.

Revised: From later comments it seems no question was explicitly posted. So I guess I should've said "Repeat your header in the body of your post"...

[moritz]

I don't think Anonymous Monk can change his postings.