From: William Kenworthy <billk@iinet.net.au>
To: Karl Trygve Kalleberg <karltk@gentoo.org>
Cc: gentoo-dev List <gentoo-dev@gentoo.org>
Subject: Re: [gentoo-dev] *-config tool renaming?
Date: Wed, 19 Nov 2003 08:24:02 +0800 [thread overview]
Message-ID: <1069201442.11518.8.camel@rattus.localdomain> (raw)
In-Reply-To: <20031118174952.GE29381@boblycat.org>
Not bad. Last time I used apropos was some years ago on on a solaris
system - I dont think its well used these days. But if it can be
highlighted in the docs enough, it will certainly help.
I would look at it as a separate issue to implementing hierarchal
naming. Downside would be ensuring all utilities have this keyword and
spreading the word.
BillK
On Wed, 2003-11-19 at 01:49, Karl Trygve Kalleberg wrote:
> On Tue, Nov 18, 2003 at 09:31:54AM +0800, Bill Kenworthy wrote:
> > The reason for using "g-" was so typing "g-<tab>" will get ALL gentoo
> > utilities. Otherwise the advantage of being consistent and hierarchal
> > is largely lost (you do need a (hopefully) short "top of tree"
> > identifier for the hierarchy). You will also need to allow for other
> > configuration tools such as g-cpan.pl which is a gentoo utility, but is
> > really perl module installer similar to emerge.
>
> Try this:
> emerge sync
> emerge gentoolkit
> makewhatis
> apropos gentoo
>
> I'll see if we can't add the Gentoo keyword to all our other tools'
> man page descriptions as well.
>
> Naturally, I think unifying the nomenclature is a good thing, but I'm
> not entirely certain I want long names for my tools. I find apropos
> to be a better solution for that.
>
>
> Kind regards,
>
> Karl T
--
William Kenworthy <billk@iinet.net.au>
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2003-11-19 0:24 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
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 [this message]
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=1069201442.11518.8.camel@rattus.localdomain \
--to=billk@iinet.net.au \
--cc=gentoo-dev@gentoo.org \
--cc=karltk@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