On 05/20/2016 12:48 PM, Michał Górny wrote: > > That's not a case since GLEP doesn't define how it is configured. > And it's invalid to reference other groups in path=s of a defined > group. >
I'm just playing language lawyer. The spec does say, A Package Manager implementing this specification must provide an ability for user to configure installed path filtering. User must be allowed to at least select well-defined paths. But "@bash-completion" is a well-defined path, and if we use the set notation, Portage users can't select it for masking. If "/" is made illegal in group names, then I could write "/*@bash-completion" instead. But we would still need to change the wording a bit to acknowledge the fact that some paths are invalid. Something like, The package manager may treat some well-defined paths as invalid, as long as an equivalent valid path exists and is accepted.
