| 1 |
On Thu, 28 Feb 2008 00:33:11 -0800 |
| 2 |
felix@×××××××.com wrote: |
| 3 |
|
| 4 |
> On Thu, Feb 21, 2008 at 03:00:50PM -0800, felix@×××××××.com wrote: |
| 5 |
> > On Thu, Feb 21, 2008 at 11:40:29PM +0100, Jes?s Guerrero wrote: |
| 6 |
> > |
| 7 |
> > > As you see, you have many alternatives. The problem with either of this, |
| 8 |
> > > is that you are the responsible to update the ebuild when necesary via svn. |
| 9 |
> > > |
| 10 |
> > > If you have questions, just ask. |
| 11 |
> > |
| 12 |
> > I just may do that :-) I will see how the new fvwm works probably |
| 13 |
> > next Wednesday, and go from there. |
| 14 |
> |
| 15 |
> Well, no luck. taskbar still segfaults: |
| 16 |
> |
| 17 |
> [ 165.614093] FvwmTaskBar[14701]: segfault at fffffff7 rip 2b7c4a6c52b5 rsp 7fff637048c0 error 4 |
| 18 |
> |
| 19 |
> [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 [1] |
| 20 |
> |
| 21 |
Then, it might be an fvwm bug. Report it at fvwm-workers@××××.org, which is |
| 22 |
the dev mailing list for fvwm, so it can be tracked and fixed. |
| 23 |
|
| 24 |
> I noticed that the fvwm overlay version is not very useful. Mplayer, |
| 25 |
> for instance, which is also part of the devnull overlay, has a useful |
| 26 |
> version: |
| 27 |
|
| 28 |
Mplayer has a version number because it's a snapshot with a given date. The fvwm is |
| 29 |
a live ebuild, which means that each time you emerge it, it download the latest code |
| 30 |
from cvs. So, if you emerge it again the next week, it will automatically update your |
| 31 |
fvwm if something has changed in cvs. |
| 32 |
|
| 33 |
Cvs/svn/git and similar ebuilds are always numbered as 9999. That's why. |
| 34 |
|
| 35 |
|
| 36 |
> |
| 37 |
> [ebuild R ] media-video/mplayer-2008.0103 |
| 38 |
> |
| 39 |
> fvwm --help is only slightly more useful: |
| 40 |
> |
| 41 |
> fvwm 2.5.25 (from cvs) compiled on Feb 21 2008 at 20:06:03 |
| 42 |
> with support for: ReadLine, Stroke, XPM, PNG, SVG, XShm, SM, Bidi text, Xinerama, XRender, XCursor, XFT, NLS |
| 43 |
> |
| 44 |
> How does it track the version internally well enough to know when |
| 45 |
> updates are available? |
| 46 |
|
| 47 |
It doesn't. You need to keep trak of the live ebuilds manually. There's an unofficial |
| 48 |
script called live-ebuilds-update or something like that. You can search the gentoo forums. |
| 49 |
I saw it around there but can't give you a link right now. |
| 50 |
|
| 51 |
> And back to fvwm, should I report this to the gentoo maintainer (who |
| 52 |
> seems to be seriously out of date) or to the fvwm project -- does |
| 53 |
> gentoo add its own bells and whistles which would make a gentoo bug |
| 54 |
> report less useful? |
| 55 |
|
| 56 |
Gentoo doesn't add too much stuff. Just a couple of patches. But it would help if you can |
| 57 |
reproduce your problem with a vanilla build of fvwm. Without patches. So we can confirm that |
| 58 |
it's an fvwm problem. |
| 59 |
|
| 60 |
With my fvwm cvs ebuild you can do this, to get a vanilla build: |
| 61 |
|
| 62 |
USE="-extras -translucency" emerge =fvwm-9999 |
| 63 |
|
| 64 |
-- |
| 65 |
Jesús Guerrero <i92guboj@×××××.es> |
| 66 |
-- |
| 67 |
gentoo-amd64@l.g.o mailing list |
Archives