Closed lizmat closed 2 years ago
I don't think
spurt "README.md",
self.readme-header ~ (slurp($file) ~ ";\npod2markdown(\$=pod)").EVAL;
should work always.
In fact, $=pod
or pod2markdown
may compile/execute $file
,
so we need to include .
in the module search paths.
https://github.com/skaji/raku-Acme-Test-Module-Zef
Here are steps to reproduce:
❯ git clone https://github.com/skaji/raku-Acme-Test-Module-Zef
❯ cd raku-Acme-Test-Module-Zef
❯ raku -MPod::To::Markdown -e '(slurp("lib/Acme/Test/Module/Zef.rakumod") ~ ";\npod2markdown(\$=pod)").EVAL;'
===SORRY!=== Error while compiling /Users/skaji/src/github.com/skaji/raku-Acme-Test-Module-Zef/EVAL_0
Could not find Acme::Test::Module::Zef2 in:
/Users/skaji/.raku
/Users/skaji/env/rakuenv/versions/2022.07-01/share/perl6/site
/Users/skaji/env/rakuenv/versions/2022.07-01/share/perl6/vendor
/Users/skaji/env/rakuenv/versions/2022.07-01/share/perl6/core
CompUnit::Repository::AbsolutePath<5864533872936>
CompUnit::Repository::NQP<5864511179384>
CompUnit::Repository::Perl5<5864511179424>
at /Users/skaji/src/github.com/skaji/raku-Acme-Test-Module-Zef/EVAL_0:2
I was about to enter a new issue, but it may be related. When I was in a module base directory which was NOT one created by App::Mi6, I ran "mi6 test" without thinking and it created a blank README.md file as it overwrote the existing one.
Maybe mi6 should check for the existence of a 'dist.ini' before running any of its run commands (similar to its current bevavior in a subdirectory of a valid mi6-managed module).
I can submit a PR if you wish, or a new issue, or both.
@lizmat
In the end, I could fix it by nuking the .precomp in the repo.
Then I think it is an issue of rakudo itself, not of mi6.
@tbrowder dist.ini is optional.
I had an issue with re-generating the
README.md
for App::Rak: it would not complain about anything, but the resultingREADME.md
only contained the header.In the end, I could fix it by nuking the
.precomp
in the repo.Before that, I could fix it by doing this patch on App::Mi6:
Is there a reason not to use this short-cut in the future?