On 05/20/2016 11:44 AM, Michał Górny wrote: > > I'd make '@' signify group names, like we do for sets. This would have > the side limitation that it would make it impossible to filter > filenames starting with '@' with the currently supported > path-or-filename syntax. >
That may be the best we can do, but in that case it's only fair to mention the exception in the GLEP. I know you don't want implementation details in there, but if *nobody* can come up with an implementation that doesn't invalidate some well-defined paths, then we should weasel-word the spec so that we don't wind up with zero fully-compliant package managers =) The @set notation isn't as much of a problem since it doesn't collide with package atoms... which gives me an idea. If we make "/" illegal in group names, then "@dir/*.*" can be interpreted as a path. That's a little better. Or, if we specify that the fnmatch pattern is applied to the absolute path, I think you can stick a leading "/*" on any pattern without loss of generality. So if you wanted to block all PDF files beginning with an "@", then instead of "@*.pdf" you could do "/*@*.pdf".
