On Thu, 28 Feb 2008 00:33:11 -0800
> On Thu, Feb 21, 2008 at 03:00:50PM -0800, felix@... wrote:
> > On Thu, Feb 21, 2008 at 11:40:29PM +0100, Jes?s Guerrero wrote:
> > > As you see, you have many alternatives. The problem with either of this,
> > > is that you are the responsible to update the ebuild when necesary via svn.
> > >
> > > If you have questions, just ask.
> > I just may do that :-) I will see how the new fvwm works probably
> > next Wednesday, and go from there.
> Well, no luck. taskbar still segfaults:
> [ 165.614093] FvwmTaskBar: segfault at fffffff7 rip 2b7c4a6c52b5 rsp 7fff637048c0 error 4
> [ebuild R ] x11-wm/fvwm-9999 USE="bidi doc gtk imlib nls perl png readline session stroke svg tk truetype xinerama xpm -debug -extras -rplay -shape -translucency" 0 kB 
Then, it might be an fvwm bug. Report it at fvwm-workers@..., which is
the dev mailing list for fvwm, so it can be tracked and fixed.
> I noticed that the fvwm overlay version is not very useful. Mplayer,
> for instance, which is also part of the devnull overlay, has a useful
Mplayer has a version number because it's a snapshot with a given date. The fvwm is
a live ebuild, which means that each time you emerge it, it download the latest code
from cvs. So, if you emerge it again the next week, it will automatically update your
fvwm if something has changed in cvs.
Cvs/svn/git and similar ebuilds are always numbered as 9999. That's why.
> [ebuild R ] media-video/mplayer-2008.0103
> fvwm --help is only slightly more useful:
> fvwm 2.5.25 (from cvs) compiled on Feb 21 2008 at 20:06:03
> with support for: ReadLine, Stroke, XPM, PNG, SVG, XShm, SM, Bidi text, Xinerama, XRender, XCursor, XFT, NLS
> How does it track the version internally well enough to know when
> updates are available?
It doesn't. You need to keep trak of the live ebuilds manually. There's an unofficial
script called live-ebuilds-update or something like that. You can search the gentoo forums.
I saw it around there but can't give you a link right now.
> And back to fvwm, should I report this to the gentoo maintainer (who
> seems to be seriously out of date) or to the fvwm project -- does
> gentoo add its own bells and whistles which would make a gentoo bug
> report less useful?
Gentoo doesn't add too much stuff. Just a couple of patches. But it would help if you can
reproduce your problem with a vanilla build of fvwm. Without patches. So we can confirm that
it's an fvwm problem.
With my fvwm cvs ebuild you can do this, to get a vanilla build:
USE="-extras -translucency" emerge =fvwm-9999
Jesús Guerrero <i92guboj@...>
email@example.com mailing list