Re: [Gnu-arch-users] Re: [PATCH] my-project-id

[Stefan Monnier]

>> tla my-project-id @gnu.org--.*/ ID1
>> tla my-project-id /emacs-- ID2
>> tla my-project-id /.*--trunk-- ID3
>> ...

> Perhaps.  I find the mandatory prefix slashes and trailing "--" an
> annoyance (although even with the regexp set syntax you need a / if
> your regexp set includes an archive regexp).

Of course, there's a price for the simplicity.

> Also, with your method, I think people will commonly make mistakes like:
>         tla my-project-id emacs ID2
> which is intended to match only project names with exactly the
> category "emacs" but which will in fact match:
>         emacs-foo--devo--1.1
> and
>         tla--emacs--1.4
> and
>         xemacs--devo--25.0

But what if someone indeed wants to match all three?  With your method
he'll have to do

      tla my-project-id .*emacs.* ID2
      tla my-project-id .*--.*emacs.* ID2

> Also, with regexp sets, it is possible to ask not only "does fully
> qualified name X match the pattern" but also "does unqualified package
> name CATEGORY--BRANCH match the pattern".

When is that needed?

>> What's wrong with tla--.*--(1\.1|1\.2\.1)$ ?
> It fails to match
>         tla--devo--1.1.1
> even though that falls between 
>         tla--devo--1.1
> and
>         tla--devo--1.2.1

Oh, sorry, I misunderstood the meaning of your suggestion.
I still think it's way overengineered, but I admit that it's
cumbersome to get the same result with regexps.


        Stefan