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 vers
> On 10 Jul 2022, at 17:38, Richard Hainsworth wrote:
> I have begun uploading modules to fez.
Good to hear!
If that is a module that was on the p6c ecosystem before, please let me know,
so that we can remove it from the p6c ecosystem.
> Suppose a module is in active development. And I have v
"The sciences, even the best,-- mathematics and astronomy,--
are like sportsmen, who seize whatever prey offers, even
without being able to make any use of it."
--Ralph Waldo Emerson, "Plato, or, the Philosopher"
The Raku Study Group
July 10, 2022 1pm in California, 9pm in the
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
Ah, indeed I did. Using App::Mi6 is so ingrained in me (and before that
"cpan-upload"), that it is hard for me to imagine any other situation :-)
Liz
> On 10 Jul 2022, at 21:41, Vadim Belman wrote:
>
> Hi,
>
> Liz has probably missed the point of your question. Yes, you must do fez
> uplo
