From: Mart Raudsepp <leio@gentoo.org>
To: gentoo-council@lists.gentoo.org
Subject: Re: [gentoo-council] GLEP 54: _live or _scm?
Date: Thu, 04 Jun 2009 01:16:27 +0300 [thread overview]
Message-ID: <1244067387.5330.1.camel@localhost> (raw)
In-Reply-To: <18982.59141.832913.549589@a1ihome1.kph.uni-mainz.de>
[-- Attachment #1: Type: text/plain, Size: 1144 bytes --]
On K, 2009-06-03 at 23:11 +0200, Ulrich Mueller wrote:
> >>>>> On Wed, 3 Jun 2009, Piotr Jaroszynski wrote:
>
> > on/after the last council meeting the biggest problem with g54
> > seemed to be whether to use scm or live suffix. I would like to do a
> > small poll here among council members so that I can edit the glep
> > accordingly. So, could you please state whether you prefer scm or
> > live?
>
> I prefer "_live" for various reasons:
>
> - Almost everybody calls them "live ebuilds" not "scm ebuilds"
> - There may be live ebuilds not related to source code management
> (app-portage/eclass-manpages might be an example), and ebuilds
> fetching their sources from a fixed tag in an SCM system, therefore
> not being live.
> - No confusion with the Scheme language.
>
> Ulrich
I prefer "live" for the same reasons above "scm" in any contexts
relating to ebuilds.
This vote (of mine) is not to be taken as an endorsement of g54 of
course, as I take it as a terminology preference question.
--
Mart Raudsepp
Gentoo Developer
Mail: leio@gentoo.org
Weblog: http://planet.gentoo.org/developers/leio
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2009-06-03 22:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-03 20:02 [gentoo-council] GLEP 54: _live or _scm? Piotr Jaroszyński
2009-06-03 21:11 ` Ulrich Mueller
2009-06-03 22:16 ` Mart Raudsepp [this message]
2009-06-03 22:46 ` Piotr Jaroszyński
2009-06-04 18:38 ` Tobias Scherbaum
2009-06-03 23:03 ` Mike Frysinger
2009-06-04 14:12 ` Doug Goldstein
2009-06-04 14:34 ` Piotr Jaroszyński
2009-06-04 1:55 ` Nirbheek Chauhan
2009-06-08 18:38 ` Petteri Räty
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=1244067387.5330.1.camel@localhost \
--to=leio@gentoo.org \
--cc=gentoo-council@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