purl-spec
purl-spec copied to clipboard
package-url
A minimal specification for purl aka. a package "mostly universal" URL, join the discussion at https://gitter.im/package-url/Lobby
This allows the PURL to specify the exact file that was used. Fixes #90.
Adds the type documentation for these repositories. Companion PR for [https://github.com/package-url/packageurl-dotnet/pull/18](https://github.com/package-url/packageurl-dotnet/pull/18) which has an update to handle the case sensitivity for these names/namespaces. Removes the duplicate empty entry for cocoapods...
Looks like the link in the README points to https://github.com/package-url/packageurl-rs (matching the others) - but that 404s as the actual rust implementation is at https://github.com/package-url/packageurl.rs It may make sense to...
it might be useful to add a PURL type for F-Droid. Currently they have ~8000 packages or so, with corresponding source code.
👋 wasn't sure where to put this, but wanted to feel out the possibility of adding some validation (optional or opt in) into the purl client libraries that would allow...
I suggest to add a version scheme `intdot` that is defined as follows: To compare 2 versions a and b, do: ``` A = a.split('.'); B = b.split('.') // split...
[PEP 503](https://peps.python.org/pep-0503/#normalized-names) specifies more detail around normalised PyPI package naming, so referencing that and reflecting the wording from it for the PyPI package-url type. Signed-off-by: Weston Steimel
Based on discussion here: https://gitter.im/package-url/Lobby?at=61ea707f46529077f596ae70
`git describe` has a nicely automatable way to determine whether a version is after a tag. However, it it not great to determine where a tag belongs (without a git...
Metadata
Owner
Metadata
A minimal specification for purl aka. a package "mostly universal" URL, join the discussion at https://gitter.im/package-url/Lobby