public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Jason Mobarak <aether@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] *-config tool renaming?
Date: Mon, 17 Nov 2003 18:13:05 -0700	[thread overview]
Message-ID: <20031118011305.GA23900@unm.edu> (raw)
In-Reply-To: <200311180026.19577.Peter.Ruskin@dsl.pipex.com>

Hi --

I vote config-* and update-* -- the other names seem a little convoluted if the
intent is to make a clear and concise tool naming scheme.

-- Jason A Mobarak (aka Aether on Freenode)

On 00:26 Tue 18 Nov     , Peter Ruskin wrote:
> On Tuesday 18 Nov 2003 00:11, Markus Nigbur wrote:
> > On Tue, 18 Nov 2003 07:18:42 +0800
> >
> > William Kenworthy <billk@iinet.net.au> wrote:
> > > I dont see a problem with branding in this case (other than
> > > gentoo-* sounding a bit ... odd!)
> > >
> > > how many other tools such as g-cpan.pl exist that few know about:
> > > is there a consolidated list of these tools and what they do? If
> > > not, some kind of consistent, hierarchal naming scheme will be a
> > > godsend!
> > >
> > > So I am suggesting
> > > g-update-etc, g-update-opengl
> > > g-install-cpan, g-install-cran
> > > g-config-distcc, g-config-java
> > > and so on
> > >
> > > BillK
> >
> > Well, the whole idea is good, but those names are really considerable
> > stupid-looking :(
> > But apparently i can't think of anything better.
> >
> > -- Markus
> 
> I think the first idea was the best: config-*
> 
> Peter
> -- 
> ======================================================================
> Portage 2.0.49-r15 (default-x86-1.4, gcc-3.2.3, glibc-2.3.2-r3, 
> 2.4.23_pre8-gss)
> i686 AMD Athlon(tm) XP 3200+
> ======================================================================
> 
> 
> --
> gentoo-dev@gentoo.org mailing list


--
gentoo-dev@gentoo.org mailing list


  reply	other threads:[~2003-11-18  1:15 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-16  9:24 [gentoo-dev] *-config tool renaming? Donnie Berkholz
2003-11-16 10:13 ` Robin H. Johnson
2003-11-16 11:00   ` Markus Nigbur
2003-11-17 14:45   ` Luca Barbato
2003-11-17 23:18     ` William Kenworthy
2003-11-17 23:22       ` Ricardo Loureiro
2003-11-18  0:11       ` Markus Nigbur
2003-11-18  0:26         ` Peter Ruskin
2003-11-18  1:13           ` Jason Mobarak [this message]
2003-11-18  1:31             ` Bill Kenworthy
2003-11-18  2:12               ` Andrew Gaffney
2003-11-18 16:10               ` Jason Mobarak
2003-11-18 17:15                 ` Donnie Berkholz
2003-11-18 17:49               ` Karl Trygve Kalleberg
2003-11-19  0:24                 ` William Kenworthy
2003-11-19  3:38                 ` Aron Griffis
2003-11-16 16:08 ` Brian Jackson
2003-11-16 18:04   ` George Shapovalov
2003-11-17  3:11 ` Jason Rhinelander
2003-11-17  4:18   ` donnie berkholz
2003-11-17 14:17     ` Gregorio Guidi
2003-11-17 15:09     ` Markus Nigbur
2003-11-17 15:32       ` Jason Stubbs
2003-11-17 21:17         ` Markus Nigbur
2003-11-17 18:24       ` Donnie Berkholz

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=20031118011305.GA23900@unm.edu \
    --to=aether@gentoo.org \
    --cc=gentoo-dev@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