Matt Donoughe

A similar thing happened with Python in #250. It makes a mess because these repository URLs are supposed to be equivalent, but how are you supposed to know when building...

The PECL page says that PECL is PEAR: > The packaging and distribution system used by PECL is shared with its sister, PEAR. https://pecl.php.net/

Not being able to install them the same way doesn't mean they aren't the same system. They use the same protocol with different repository_urls (channels). ``` $ pear channel-info pecl.php.net...

If the namespace of the PURL contains information for channel discovery, how does it interact with repository_url qualifier? Does repository_url override the base URL that would normally be determined through...

It would be nice to have this functionality moved forward from the XMLRPC API, both `package_roles(package_name)` and `user_packages(user)`, with the roles included.

> However, the examples (e.g. for _golang_) seem to be [contradicting that](https://github.com/package-url/purl-spec/blob/master/PURL-TYPES.rst#golang): There is no contradiction. 1. "percent-encoded string" does not specify whether `/` is supposed to be encoded or...

Percent encoding lists no reserved characters. `/` is a reserved character in a URI, but even then it is not always encoded (in fact, Python's percent encoding function by default...

You're apparently looking at a different Wikipedia. Mine does not list any reserved characters for percent encoding in general, and also clarifies that "reserved" does not mean escaped: > When...

> * Each namespace segment must be a percent-encoded string > * A name must be a percent-encoded string > > So name and namespace are encoded in the same...

Percent encoding is supposed to work differently depending on whether it's the namespace or the name, and this is something that is often confusing. It'd be nice if the spec...