From: Dan Naumov <jago@telefragged.com>
To: gentoo-dev@gentoo.org
Subject: [gentoo-dev] Portage directory hierarchy and XMMS visualisation plugins.
Date: Tue, 28 May 2002 01:54:24 +0300 [thread overview]
Message-ID: <20020528015424.63d8dccf.jago@telefragged.com> (raw)
Hello.
I wasn't able to find out who I should contact about this matter, so I subscribed to this list hoping that my concern will reach the right person. If I mistaken, please don't shoot me, but rather point me in the correct direction 8)
After emerging several XMMS visualisation plugins, I've noticed that all of them are located under /portage/media-sound which IMHO, doesn't make much sense seeing as while they're related to an audio program, they're more related to video by themselves. I think it would be better if the XMMS audio-related plugins were kept separated from the visualisations, ie. audio plugins in media-audio and visualisations in media-video. These plugins are also kept separate in the FreeBSD ports system.
If all XMMS plugins continue to go under media-sound, it will soon be very hard to figure out which are which when browing the portage hierarchy. There are already 14 plugins under media-sound and things start getting confusing for people like me, who prefer to browse the Portage tree "manually" looking for new software rather then using "emerge -s".
Anyways, just thought I'd share my opinion.
Sincerely,
Dan Naumov (aka Jago on OPN)
P.S: I also think that people with commit access to the portage cvs should be provided with clear guidelines on what things go where.
P.P.S: Thanks for the great distro 8)
next reply other threads:[~2002-05-27 22:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-27 22:54 Dan Naumov [this message]
2002-05-27 23:11 ` [gentoo-dev] Portage directory hierarchy and XMMS visualisation plugins Ben Lutgens
2002-05-28 1:30 ` Dan Naumov
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=20020528015424.63d8dccf.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