| 1 |
Hi -- |
| 2 |
|
| 3 |
I vote config-* and update-* -- the other names seem a little convoluted if the |
| 4 |
intent is to make a clear and concise tool naming scheme. |
| 5 |
|
| 6 |
-- Jason A Mobarak (aka Aether on Freenode) |
| 7 |
|
| 8 |
On 00:26 Tue 18 Nov , Peter Ruskin wrote: |
| 9 |
> On Tuesday 18 Nov 2003 00:11, Markus Nigbur wrote: |
| 10 |
> > On Tue, 18 Nov 2003 07:18:42 +0800 |
| 11 |
> > |
| 12 |
> > William Kenworthy <billk@×××××××××.au> wrote: |
| 13 |
> > > I dont see a problem with branding in this case (other than |
| 14 |
> > > gentoo-* sounding a bit ... odd!) |
| 15 |
> > > |
| 16 |
> > > how many other tools such as g-cpan.pl exist that few know about: |
| 17 |
> > > is there a consolidated list of these tools and what they do? If |
| 18 |
> > > not, some kind of consistent, hierarchal naming scheme will be a |
| 19 |
> > > godsend! |
| 20 |
> > > |
| 21 |
> > > So I am suggesting |
| 22 |
> > > g-update-etc, g-update-opengl |
| 23 |
> > > g-install-cpan, g-install-cran |
| 24 |
> > > g-config-distcc, g-config-java |
| 25 |
> > > and so on |
| 26 |
> > > |
| 27 |
> > > BillK |
| 28 |
> > |
| 29 |
> > Well, the whole idea is good, but those names are really considerable |
| 30 |
> > stupid-looking :( |
| 31 |
> > But apparently i can't think of anything better. |
| 32 |
> > |
| 33 |
> > -- Markus |
| 34 |
> |
| 35 |
> I think the first idea was the best: config-* |
| 36 |
> |
| 37 |
> Peter |
| 38 |
> -- |
| 39 |
> ====================================================================== |
| 40 |
> Portage 2.0.49-r15 (default-x86-1.4, gcc-3.2.3, glibc-2.3.2-r3, |
| 41 |
> 2.4.23_pre8-gss) |
| 42 |
> i686 AMD Athlon(tm) XP 3200+ |
| 43 |
> ====================================================================== |
| 44 |
> |
| 45 |
> |
| 46 |
> -- |
| 47 |
> gentoo-dev@g.o mailing list |
| 48 |
|
| 49 |
|
| 50 |
-- |
| 51 |
gentoo-dev@g.o mailing list |
Archives