Vadim and Liz,
Thank you for this clue.
I seem to be behind on this. I do not use App::Mi6
I try to keep to the documentation on Modules.pod6, and I have updated
Modules.pod6 every time I learn something more.
It seems to me that there should be some more explanation in
Modules.pod6 for sharing a module, including some ideas about how to use
App::Mi6
I looked at module development utilities (modules-extra.pod6), but it is
so minimalist that it is meaningless to me.
Richard
On 10/07/2022 8:41 pm, Vadim Belman wrote:
Hi,
Liz has probably missed the point of your question. Yes, you must do fez upload
for each new release. It means each time you'd need to do some pre-release
preparations to create an archive, etc... The fastest way is to switch to
App::Mi6 for building distributions. My approach is a makefile plus helper
scripts I include as a submodule for nearly each project I develop because mi6
doesn't cover my needs.
Best regards,
Vadim Belman
On Jul 10, 2022, at 11:38 AM, Richard Hainsworth wrote:
I have begun uploading modules to fez.
Suppose a module is in active development. And I have v0.7.1, then v0.7.2 etc.
Do I need to upload each version, or will fez automatically provide the most
updated module?
When p6c was the main ecosystem, the reference was to github. So, the latest
version on github was used, and zef would use whatever was on github.
