public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: [gentoo-dev] More info than DESCRIPTION
Date: Thu, 19 Jun 2003 19:26:28 -0400	[thread overview]
Message-ID: <200306191926.28901.vapier@gentoo.org> (raw)

sometimes its nice to see what a package does ... and i mean more than a 
1-liner ... for example the way rpm stores a large description in itself ...

i like having the 1-liner short description, dont get me wrong ... i dont want 
to see that change ... but what if we were to add support for a large 
description/explanation for ppl who are not familiar with it ...

could be handled in a couple of ways:
1. a package you would emerge that would have a large database of descriptions 
... not very good idea due to updating 1 package means a whole new d/l ...
2. a package that would query a remote gentoo server via http or something
3. another file for all packages to be added to cvs ... say 'Info' or 'About' 
or something similar ... i would rather not see it go into the ebuild ;)

<[Eazy|E]> is there a way to get an info about the package, the info like the 
freshmeat.net gives out ?
<[Eazy|E]> I liked the way rpm's had info stored about the package, so one who 
does not know the package can get an overview of the package with the text 
w/o checking the homepage etc
<[Eazy|E]> since qpkg can query the packages, it could be used also for giving 
more info about the package, like -i, maybe just another flag that will spit 
out more text etc.

thoughts/etc... ?
-mike

--
gentoo-dev@gentoo.org mailing list


             reply	other threads:[~2003-06-19 23:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-19 23:26 Mike Frysinger [this message]
2003-06-19 23:49 ` [gentoo-dev] More info than DESCRIPTION Thomas de Grenier de Latour
2003-06-19 23:51   ` Mike Frysinger
2003-06-19 23:49 ` Alastair Tse
2003-06-20  8:41   ` Paul de Vrieze

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=200306191926.28901.vapier@gentoo.org \
    --to=vapier@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