public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Robin H. Johnson" <robbat2@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [PMS] Version Naming Clarification
Date: Thu, 7 Jun 2007 11:28:26 -0700	[thread overview]
Message-ID: <20070607182826.GC3401@curie-int.orbis-terrarum.net> (raw)
In-Reply-To: <46684898.6070805@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 1448 bytes --]

On Thu, Jun 07, 2007 at 02:04:08PM -0400, Doug Goldstein wrote:
> > Thing is: if you see sys-fs/ntfs-3g, is that an atom or a CPV? You
> > don't know unless you actually check the tree.
> I thought that was the whole point of =. That identifies CPV instead of
> an atom.
If you look the DEPEND/RDEPEND portion of ebuilds,
there are a lot of deps just declared as CAT/PN, with no version
numbering.

I think this might be a clearer version of what you are trying to say.
1. Given a string S that is 'XXXXXXXXXXXXX' 
2. If S starts with an operator (=,>,>=,<=,<), then S MUST have a
   version number on the end. S is of the form: CAT/PN-PV(-PR), where
   both CAT and PN may contain a -. PR is optional, and must be of the
   form /^-r[[:digit:]]+$/
3. If S does not start with an operator, then S is of the form:
   CAT/PN, where CAT and PN may contain a -.
4. If the first character was a !, then remember that, strip the ! from
   S, and repeat from 2.
5. If you reach this point, you have something that is not valid.

This means if somebody specified:
sys-fs/ntfs-3g-1.516
The CAT is 'sys-fs'
and the PN is 'ntfs-3g-1.516'
which does not exist.

I can't see any logical problems with the above. It probably makes
things a lot easier in many places.

-- 
Robin Hugh Johnson
Gentoo Linux Developer & Council Member
E-Mail     : robbat2@gentoo.org
GnuPG FP   : 11AC BA4F 4778 E3F6 E4ED  F38E B27B 944E 3488 4E85

[-- Attachment #2: Type: application/pgp-signature, Size: 321 bytes --]

  reply	other threads:[~2007-06-07 18:31 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-07 13:56 [gentoo-dev] [PMS] Version Naming Clarification Doug Goldstein
2007-06-07 14:31 ` Doug Goldstein
2007-06-07 16:32 ` Daniel Drake
2007-06-07 17:42   ` Marius Mauch
2007-06-07 17:57     ` Georgi Georgiev
2007-06-07 18:50       ` Marius Mauch
2007-06-07 18:04     ` Doug Goldstein
2007-06-07 18:28       ` Robin H. Johnson [this message]
2007-06-07 19:04         ` Doug Goldstein
2007-06-07 20:01           ` Carsten Lohrke
2007-06-07 20:12             ` Matti Bickel
2007-06-07 20:14             ` Doug Goldstein
2007-06-07 20:50               ` Carsten Lohrke
2007-06-07 20:17           ` Marius Mauch
2007-06-07 20:25         ` Marius Mauch
2007-06-07 20:32     ` Stephen Bennett
2007-06-07 20:33       ` Harald van Dijk
2007-06-07 20:40         ` Ciaran McCreesh
2007-06-07 20:52           ` Harald van Dijk
2007-06-07 21:15             ` Ciaran McCreesh
2007-06-07 21:31               ` Harald van Dijk
2007-06-07 21:38                 ` Ciaran McCreesh
2007-06-07 22:18                   ` Stephen Bennett
2007-06-07 22:48                     ` Doug Goldstein
2007-06-07 21:10         ` Stephen Bennett

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=20070607182826.GC3401@curie-int.orbis-terrarum.net \
    --to=robbat2@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