From: Dan Naumov <jago@telefragged.com>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Portage directory hierarchy and XMMS visualisation plugins.
Date: Tue, 28 May 2002 04:30:57 +0300 [thread overview]
Message-ID: <20020528043057.1fc064af.jago@telefragged.com> (raw)
In-Reply-To: <20020527231141.GG24425@rtfm.sistina.com>
> In my opinion there aren't enough of them to warrant thier own
> directory.
I don't think they need a completely new directory. Having the audio plugins in media-audio and the visualisations in media-video would do the job nicely.
> Why would you search manually when we have emerge -s?
Because "emerge -s" only shows you things you know are already there, you must provide some kind of an argument like "emerge -s foo" to find something. When I want some new piece of software I've never used and possibly, never ever heard of, I would just emerge rsync and go browsing the portage tree using "cd" and "ls" just to see whats in there.
Sincerely,
Dan Naumov
prev parent reply other threads:[~2002-05-28 1:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-27 22:54 [gentoo-dev] Portage directory hierarchy and XMMS visualisation plugins Dan Naumov
2002-05-27 23:11 ` Ben Lutgens
2002-05-28 1:30 ` Dan Naumov [this message]
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=20020528043057.1fc064af.jago@telefragged.com \
--to=jago@telefragged.com \
--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