An idea for meson wrap init <your-project>
for generating a wrap file for a given project
#13254
Replies: 2 comments 1 reply
-
Wrap files don't describe project options to begin with. Nor version numbers, actually, except inasmuch as the wrapdb associates a wrap file to the upstream project version it is tied to. Version numbers are usually part of the url but that isn't a requirement. As far as hash values go, meson will print the hash value it actually got when a failed download happens, so you can just copy that. But it doesn't seem quite practical to generate a wrap file without knowing what url to use. So I don't know how you want to generate them. It also doesn't answer the problem of defining the right |
Beta Was this translation helpful? Give feedback.
-
Could add sub-arguments for the [provide] section and other bits of info. Something like: meson wrap init <wrap name> --provide <project_dep_value>
meson wrap init <wrap name> --provide <project_dep_value> --version <xyz>
meson wrap init <wrap name> --provide <project_dep_value> --type <git/wrap/svc> |
Beta Was this translation helpful? Give feedback.
-
What if we had Meson help generate the wrap files? Realistically it would know more information about a project like version number, what options are defined, and other attributes, and it would probably put an end to broken hash values using its sanity check system.
Beta Was this translation helpful? Give feedback.
All reactions