From: Ernst Herzberg <earny@net4u.de>
To: Vadim <vadim_t@teleline.es>, gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Horrible package descriptions
Date: Fri, 23 May 2003 01:20:14 +0200 [thread overview]
Message-ID: <200305230120.14640.earny@net4u.de> (raw)
In-Reply-To: <200305230006.23949.vadim_t@teleline.es>
On Freitag, 23. Mai 2003 00:06, Vadim wrote:
> Sure, that sometimes works. But not always. I can think of multiple
> problems with that. For example:
>
> That assumes that the web site says something useful about it. It might
> be a site from somebody who just put his/her stuff on the web in case
> somebody find it useful, with no documentation at all. Or it might
> happen to be some obscure tiny tool made by a large company that's got a
> huge site where you have to search for 15 minutes until your find
> something.
>
> Sometimes, you have network problems too. The site might be down. Or
> have moved somewhere else. Or perhaps you have a local Gentoo mirror and
> no internet connection due to problems/paranoid security.
>
> Then, there is a problem with searching. I'd like to be able to find
> SAMBA without knowing how it, or the protocol is called. Most people
> might try to search for "windows network", for example. The URL is not
> very helpful when you know what kind of tool you want, but not the exact
> tool.
Put the long descriptions in a separate package, like a gentoo description
database. If somebody need it, he can emerge it. Then the portage tree
will not grow because of the long descriptions, and you can split the
descrition database for example in pieces, so you dont have to download
the complete database if one package description changes.
If emerge -S find such a database, it will search that too, if not, then
not ;-)
If somebody even has enough sparetime, this package can be easy extended,
for example to search also a database on the net..
... only thinking....
<Earny>
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2003-05-22 23:20 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-22 22:06 [gentoo-dev] Horrible package descriptions Vadim
2003-05-22 23:20 ` Ernst Herzberg [this message]
2003-05-23 2:55 ` John Nilsson
-- strict thread matches above, loose matches on Subject: below --
2003-05-22 18:12 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
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
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=200305230120.14640.earny@net4u.de \
--to=earny@net4u.de \
--cc=gentoo-dev@gentoo.org \
--cc=vadim_t@teleline.es \
/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