Re^2: Build.PL usage during module authoring

All I got out of that was that you run perl Build again.

john@makemake:~/dev/HTML-EntityReference$ perl Build
Building HTML-EntityReference
john@makemake:~/dev/HTML-EntityReference$ ./Build
Building HTML-EntityReference
john@makemake:~/dev/HTML-EntityReference$ ./Build test
t/00-load.t ...... 1/1
#   Failed test 'use HTML::EntityReference;'
#   at t/00-load.t line 6.
#     Tried to use 'HTML::EntityReference'.
#     Error:  Can't locate HTML/Entity-HTML5_draft.inc.pl in @INC (@IN
+C contains: /var/content/dev/HTML-EntityReference/blib/lib /var/conte
+nt/dev/HTML-EntityReference/blib/arch /etc/perl /usr/local/lib/perl/5
+.10.1 /usr/local/share/perl/5.10.1 /usr/lib/perl5 /usr/share/perl5 /u
+sr/lib/perl/5.10 /usr/share/perl/5.10 /usr/local/lib/site_perl) at /v
+ar/content/dev/HTML-EntityReference/blib/lib/HTML/EntityReference.pm 
+line 345.
# Compilation failed in require at (eval 4) line 2.
# BEGIN failed--compilation aborted at (eval 4) line 2.
Bailout called.  Further testing stopped:
# Testing HTML::EntityReference 0.010, Perl 5.010001, /usr/bin/perl
# Looks like you failed 1 test of 1.
FAILED--Further testing stopped.
john@makemake:~/dev/HTML-EntityReference$
[download]

I can delete blib, and running perl Build will make it reappear. It contains the main .pm file, but not the other files I have in the original lib directory, even though the one I'm interested in is named in the Manifest.

Maybe it only copies files with a .pm extension? Your example added another module to the tree, not an internal file that would be "required".

Comment on Re^2: Build.PL usage during module authoring Select or Download Code

Replies are listed 'Best First'.
Re^3: Build.PL usage during module authoring by Anonymous Monk on May 13, 2011 at 02:39 UTC
Maybe it only copies files with a .pm extension? Your example added another module to the tree, not an internal file that would be "required". Yes it does, and that is a good thing. Why? Because copying .pl files by default is an often overlooked and most surprising feature of ExtUtils::MakeMaker , new authors just don't expect it, and they forget to check blib Read more... (1250 Bytes) If you want Module::Build to do the same, you'll have to be proactive, one way is Module::Build::Cookbook#Adding new file types to the build process. Also, consider Module::Build::API#share_dir or AutoSplit Oh, and now is a good time to review How do I post a question effectively? :)	[reply] [d/l]
Re^4: Build.PL usage during module authoring by John M. Dlugosz (Monsignor) on May 13, 2011 at 02:53 UTC
>> Oh, and now is a good time to review How do I post a question effectively? :) I did say “But I added another file in the same directory as the .pm file, that is "required" by the code at run time”. I did not say that I was adding another module to the distribution; it was "some file", and although I didn't spell it out, it should have been clear that whatever it was, it was not a .pm file. So maybe you can stop hiding behind Anonymous, and perhaps read a little more closely and answer what was asked. Or be a little more polite with pointing out that the root of the problem wasn't as explicit as it could have been (after all, had I know it was significant I would have known what to look for!!) rather than treating a 10-year PM veteran like a noob.	[reply]
Re^5: Build.PL usage during module authoring by Anonymous Monk on May 13, 2011 at 03:25 UTC
The premise of How do I post a question effectively? is to remove guessing by providing replicable details. If you show code, a patch, a set of shell commands... there isn't any guessing involved as to what you're doing and how its a problem. How many times in your 10 years have you read How do I post a question effectively?	[reply]