Prepare for zef ecosystem

[vrurg]

• start using mi6 for release
• keep auth/ver/api of the module in sync with META6.json
• add Changes file
• change auth to zef:raku-community-modules

[vrurg]

Next step: switch to using main branch. Then version bump and release.

[vrurg]

Is there a spec for the Changes format? I favor lowercase list items

I never seen a spec. There is no even single file name standard out there. :)

[abraxxa]

Is there a spec for the Changes format? I favor lowercase list items

I never seen a spec. There is no even single file name standard out there. :)

There is one for Perl 5: https://metacpan.org/dist/CPAN-Changes/view/lib/CPAN/Changes/Spec.pod

[vrurg]

Quite amusingly, all examples are using capitalized lines. :)

[rbt]

Looks like this broke the tests on HEAD.

Perhaps just delete the 01-Basic.t test for:

not ok 5 - Greater than v.0.0.0, (v*)

[vrurg]

Perhaps just delete the 01-Basic.t test for:

But it does pass tests for me on both macOS and linux. Otherwise mi6 wouldn't even allow releasing.

[rbt]

https://github.com/raku-community-modules/DBIish/actions/runs/1989228809

Perhaps it's the github actions that need to change then?

[vrurg]

Perhaps it's the github actions that need to change then?

(facepalm) Actually, yes, it needs. With a valid META6 prove6 must be used with -I. instead of -l. Can you try it? I wouldn't be able for a couple of coming hours.

[rbt]

(With a valid META6 prove6 must be used with -I. instead of -l.

That worked. Pushed.

[vrurg]

Actually I meant exactly -I.. It's quite fundamental difference because this way modules are getting found based on META6 content whereas -Ilib makes them found based on file system content.

Basically, -I. gives path to distribution location.

So far, as it works for testing, let it be. I'll try to remember to try the other way sometime.