public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Michael Orlitzky <mjo@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [RFC] New GLEP: file installation masks
Date: Fri, 20 May 2016 12:15:36 -0400	[thread overview]
Message-ID: <573F3828.3020906@gentoo.org> (raw)
In-Reply-To: <20160520174428.18c0ed8d@pomiocik>

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".



  reply	other threads:[~2016-05-20 16:15 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-20 14:01 [gentoo-dev] [RFC] New GLEP: file installation masks Michał Górny
2016-05-20 15:12 ` Michael Orlitzky
2016-05-20 15:21   ` Michał Górny
2016-05-20 15:30     ` Michael Orlitzky
2016-05-20 15:44       ` Michał Górny
2016-05-20 16:15         ` Michael Orlitzky [this message]
2016-05-20 16:48           ` Michał Górny
2016-05-20 17:34             ` Michael Orlitzky
2016-05-29 12:54               ` Michał Górny
2016-05-20 15:34 ` Daniel Campbell
2016-05-20 15:40   ` Michael Orlitzky
2016-05-20 15:49     ` Michał Górny
2016-05-20 20:00       ` Ian Stakenvicius
2016-05-20 21:11         ` Michał Górny
2016-06-08  5:26 ` [gentoo-dev] " Ulrich Mueller
2016-06-08  6:37   ` Michał Górny
2016-06-08  7:17     ` Ulrich Mueller
2016-06-08  8:01       ` Michał Górny
2016-06-08  8:33         ` Ulrich Mueller
2016-06-08 13:14           ` Michał Górny

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=573F3828.3020906@gentoo.org \
    --to=mjo@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox