public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ben Lutgens <lamer@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Portage directory hierarchy and XMMS visualisation plugins.
Date: Mon, 27 May 2002 18:11:41 -0500	[thread overview]
Message-ID: <20020527231141.GG24425@rtfm.sistina.com> (raw)
In-Reply-To: <20020528015424.63d8dccf.jago@telefragged.com>

[-- Attachment #1: Type: text/plain, Size: 2487 bytes --]

On Tue, May 28, 2002 at 01:54:24AM +0300, Dan Naumov wrote:
>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)

This probably the best place.

>
>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.
>

In my opinion there aren't enough of them to warrant thier own directory.
I think they should all be in x11-misc or perhaps a media-misc. To simplify
the install you can (or one of the developers can) create a virtual package
that DEPENDS on all the other plugins. Perhaps I'll do that today.

>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".
>

Why would you search manually when we have emerge -s?

>Anyways, just thought I'd share my opinion.

Your opinion is very welcome! 

>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.

That's a wee-bit presumptuous of you IMHO. What makes you think we don't
have "guidance" on what things go where? Just because it doesn't make sense
to you, that doesn't mean we lack leadership or direction. Many moons ago
we had things setup very differently in the tree. It seemed we were getting
new directories every week and it got a bit cumbersome. We settled on this,
at some point it may need to be changed again. Untill then, we go with what
we have.

-- 
Ben Lutgens				 | http://people.sistina.com/~blutgens/	
System Administrator	 | http://www.sistina.com/
Sistina Software Inc. | 

"I got a wife and kids too but you don't see me out here stealing Imperial
Droids now do ya?"

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2002-05-27 23:11 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 [this message]
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=20020527231141.GG24425@rtfm.sistina.com \
    --to=lamer@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