Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 10499 - Eterm as dependency for waimea-ebuilds
Summary: Eterm as dependency for waimea-ebuilds
Status: RESOLVED WONTFIX
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: All Linux
: High trivial (vote)
Assignee: Matt Keadle
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-11-09 17:32 UTC by Johannes Steinkraus
Modified: 2003-06-18 23:12 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Johannes Steinkraus 2002-11-09 17:32:23 UTC
Waimea needs "Esetroot" from Eterm to set the background(-colors).
Eterm should be a dependency for emerging waimea, maybe you'll fix
this?
Comment 1 Seemant Kulleen (RETIRED) gentoo-dev 2002-11-16 04:51:36 UTC
and *box as well, I think.

matt: any thoughts to the virtual/imageviewer dealy?
Comment 2 Matt Keadle 2002-11-21 20:50:45 UTC
I think the issue of Waimea needing Eterm and the idea of creating
virtual/imageviewer are mutualy exclusive. Here's why..

First off, Wiamea does _not_ need Esetroot from the eterm package. The original
reporter makes it sound as if Esetroot is the only application that can
successfuly set the root image/color in Waimea. This is completely untrue, as
`xsetroot -solid black` works just as well. If Esetroot was in fact the only way
to set a root image/color in Waimea then there would be no question. In that
case it should be a dependancy. Also, the *boxes work just as well with
xsetroot. This leads me to another point.

I fear the bloat. Yes, Esetroot is a great X root image tool, but it is not
required. More so, just to get Esetroot you have to bring in the entire eterm
package. As Seemant knows I've already looked at the possibility of moving
Esetroot into commonbox-utils and it just is not possible. Also, I, like many
others, do not use eterm (or aterm for that matter). If I don't use them then I
don't want them on my machine. Personally, I think it's a very big jump to force
Waimea to require eterm just because Esetroot sets a nice root image when others
work fine. The same goes for the *boxes. In my mind xsetroot is fully capable of
setting a nice color background. If you want to display pretty images then users
are fully allowed to emerge their tool of choice, but I'm somewhat very against
forcing programs onto a users box, especially for the sake of one small tool
that comes with the package.

As for virtual/imageviewer, my feelings are largely the same. If there is a case
where an imageviewer is *required* by a package to work then I'm all for it.
Otherwise I worry that (if this practice is put to use in other areas) users
will end up with a ton of software on their machines that is barely taken
advantage of and only servers a minor purpose. If users desire features they are
welcome to have them if they are available, but by forcing programs as deps it
cheats those who don't want that stuff out of their slim, efficient well
controlled machines.

As a reference I use Openbox with a very simple style, no root image, and rxvt
as my terminal.
Comment 3 Matt Keadle 2002-12-10 14:41:04 UTC
I'm looking into puting a default style for Waimea into commonbox-styles that
does not rely on Esetroot to set the root image. Commonbox-styles will then
become a dep of Wiamea instead of eterm.
Comment 4 Matt Keadle 2003-06-18 23:12:37 UTC
waimea looks like a dead project and pulling in Eterm for just for Esetroot is a bit out there. also, modding commonbox and modding waimea seem more and more like beating a dead horse.