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] [GLEP] scm package version suffix
Date: Mon, 10 Dec 2007 00:36:04 -0800	[thread overview]
Message-ID: <20071210083604.GG14557@curie-int.orbis-terrarum.net> (raw)
In-Reply-To: <20071210082427.503cf5a1@blueyonder.co.uk>

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

On Mon, Dec 10, 2007 at 08:24:27AM +0000, Ciaran McCreesh wrote:
>     mypkg-scm
One devil's advocate question for now.
Regardless of which suffix we pick, given that it is a well-known
suffix, what will be the expected behavior when PN = 'foo-scm'?

There's at least one package on Freshmeat with that name (vrml-scm), and
I have seen another one elsewhere when researching Git conversion tools.

-- 
Robin Hugh Johnson
Gentoo Linux Developer & Infra Guy
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-12-10  8:39 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-09 16:01 [gentoo-dev] [GLEP] scm package version suffix Piotr Jaroszyński
2007-12-09 16:18 ` Josh Sled
2007-12-09 17:22   ` Piotr Jaroszyński
2007-12-09 17:52 ` Petteri Räty
2007-12-09 18:00   ` Piotr Jaroszyński
2007-12-09 18:45 ` Jan Kundrát
2007-12-09 18:57   ` Ciaran McCreesh
2007-12-10  4:31     ` Donnie Berkholz
2007-12-10  7:18       ` Ciaran McCreesh
2007-12-10  7:44         ` Nirbheek Chauhan
2007-12-10  8:24           ` Ciaran McCreesh
2007-12-10  8:36             ` Robin H. Johnson [this message]
2007-12-10  8:44               ` Ciaran McCreesh
2007-12-11  1:12             ` [gentoo-dev] " Ryan Hill
2007-12-10 12:59           ` [gentoo-dev] " Robert Buchholz
2007-12-10 14:24             ` Nirbheek Chauhan
2007-12-10 15:14               ` Robert Buchholz
2007-12-10 19:44                 ` Nirbheek Chauhan
2007-12-10 19:49                   ` Nirbheek Chauhan
2007-12-11  0:27                   ` [gentoo-dev] " Steve Long
2007-12-11 10:59                     ` Nirbheek Chauhan
2007-12-11 11:03                     ` Nirbheek Chauhan
2007-12-11  8:21                   ` Duncan
2007-12-11 11:06                     ` Nirbheek Chauhan
2007-12-11 11:17                       ` Ciaran McCreesh
2007-12-11 12:10                         ` Nirbheek Chauhan
2007-12-10  8:26         ` [gentoo-dev] " Robin H. Johnson
2007-12-10  8:34           ` Ciaran McCreesh
2007-12-10  9:21           ` [gentoo-dev] Handling branch strings Donnie Berkholz
2007-12-10  9:34             ` Santiago M. Mola
2007-12-10 19:42               ` Donnie Berkholz
2007-12-11  1:35                 ` [gentoo-dev] " Ryan Hill
2007-12-11  8:11                 ` [gentoo-dev] " Ciaran McCreesh
2007-12-11 11:46                   ` Santiago M. Mola
2007-12-11 17:56             ` [gentoo-dev] " Christian Faulhammer
2007-12-09 19:38   ` [gentoo-dev] Re: [GLEP] scm package version suffix Ryan Hill

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=20071210083604.GG14557@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