New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Solidify and document META6.json content #764
Comments
|
Some potential fixes: |
|
FWIW, all modules without source-url: |
|
I've fixed last module. But I personally 👍 the idea about providing a common pattern for |
|
Did we already decide what counts as “fixing”? |
|
Like, there are currently 680 modules. If we decide that I don't think that the method of least resistance has any significant benefits on this stage. I'd much rather prefer solution that we can call “right” for many years to come. |
So far the conversation reached this: However, the source-url for all currently-added ecosystem modules can be derived from the META file URL, so I'd fix panda (and ufo, if it needs fixing) and that will let us consider |
|
Actually, we may not even need to fix panda, but rather ensure the ecosystem generator panda uses fills in a |
Dummy module for ecosystem toolchain testing. Related to Raku/doc#764
Dummy module for ecosystem toolchain testing. Related to Raku/doc#764
Dummy module for ecosystem toolchain testing. Related to Raku/doc#764
|
Can someone check if META6.json is solid enough? Either that, or totally melted. It's been two years... |
|
I guess it's more about this section: https://docs.perl6.org/language/modules#index-entry-META6.json-META6.json |
|
|
|
That should be done then to close this issue (perhaps ask on #perl6 if |
|
|
|
@JJ see also this: https://irclog.perlgeek.de/perl6-dev/2018-03-18#i_15935872 |
|
though it might somewhat out of date |
We need to solidify what should be inside META6.json file, what format everything is, and what is optional and what is mandatory—and that should be well documented.
Based on this IRC conversation, what goes into META6.json is a bit muddy at the moment.
Based on ugexe's comments, the currently described S22 META6.json is up-to-date, except for what the
resourcesproperty takes.The properties we list in the documentation however are different. I think they talk about the old
resourcesformat and they still mention no-longer speccedsource-urlkey.The new alternative for
source-urlis"support: { "source": .... However, only 26 modules out of 680 actually use it. Worse, it's specced as optional, however, panda will die if it cannot find eithersource-urlorsupport.sourceand from what I recall, the modules.perl6.org dist builder will also have issues with dists that lack any source URLs in META.So part of this Issue would be either changing the spec and making some kind of source URL mandatory or fixing our tooling.
My suggestion would be to go with least resistance and remove optional
support.sourceproperty while adding a mandatorysource-urlproperty.The text was updated successfully, but these errors were encountered: