public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Matt Tucker <tuck@whistlingfish.net>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Horrible package descriptions
Date: Thu, 22 May 2003 13:59:31 -0700	[thread overview]
Message-ID: <28320000.1053637171@nareau.whistlingfish.net> (raw)
In-Reply-To: <20030523194036.GA5511@noa.neverborn.ORG>

-- "leon j. breedt" <ljb@neverborn.org> spake thusly:

> that said, I'm not sure how much use a long description would be to
> me. the DESCRIPTION, along with the category/group, give me enough of
> a context to be able to fill in the blanks for most ebuilds.  the only
> time I've actually read the description on other distributions was
> when browsing using a GUI tool :)

Keep in mind that another thing long descriptions are good for (as
Vadim pointed out in the original post) is something else to search
against. For instance, if I wanted to find something that plays
quicktime movies, I might search against 'quicktime'. Doing this on
Gentoo yields:

    libquicktime, openquicktime, quicktime4linux

which isn't really all that useful. If I search against the
description, (which takes far, FAR too long -- almost 2 minutes -- this
data really needs to be indexed), I get:

    libquicktime, openquicktime, quicktime4linux, xanim-export, xmovie

On Debian, I get:

    quicktime-x11utils, libquicktime1, xawtv-plugin-qt,
    libquicktime-dev, xmovie, dv-utils, dvgrab, xanim-modules,
    xawtv, xine-ui, kino, libxine1, libxine-dev, camstream,
    xanim, gnome-xine,

which shows quite a bit more, including a player that's worth using.
Sure, you could suggest that I formulate a better search, but often
this requires extra knowledge that a user may not have.

I recall that when I was running Debian and wanted to find a package
that did something I needed, I'd do 'apt-cache search'. On Gentoo I
usually end up going to Freshmeat or Google to find the package, and
then check to see whether there's an ebuild for it. This is not, in my
opinion, an ideal situation. It's particularly frustratring when just
getting started on Gentoo and trying to find all those tools you're
used to.


--
gentoo-dev@gentoo.org mailing list


  reply	other threads:[~2003-05-22 20:59 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-22 18:12 [gentoo-dev] Horrible package descriptions Vadim
2003-05-22 18:23 ` oford
2003-05-22 18:31 ` Dhruba Bandopadhyay
2003-05-22 19:01   ` John Robinson
2003-05-22 19:07     ` Seemant Kulleen
2003-05-22 20:28   ` Spundun Bhatt
2003-05-22 18:34 ` Sven Vermeulen
2003-05-22 18:56   ` Dylan Carlson
2003-05-22 19:02     ` Paul de Vrieze
2003-05-22 19:11       ` Dylan Carlson
2003-05-22 19:17         ` Paul de Vrieze
2003-05-23  2:04       ` Frantz Dhin
2003-05-23 19:40       ` leon j. breedt
2003-05-22 20:59         ` Matt Tucker [this message]
2003-05-23 10:23           ` Sven Vermeulen
2003-05-22 19:17   ` Matthew Kennedy
2003-05-22 19:19   ` Matthew Kennedy
2003-05-22 19:34     ` Paul de Vrieze
  -- strict thread matches above, loose matches on Subject: below --
2003-05-22 22:06 Vadim
2003-05-22 23:20 ` Ernst Herzberg
2003-05-23  2:55   ` John Nilsson

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=28320000.1053637171@nareau.whistlingfish.net \
    --to=tuck@whistlingfish.net \
    --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