I used to have fvwm2 binary whereas now only fvwm exists which in turn means that I had to edit ~/.xsession and rename fvwm2 in there to fvwm. Is that intentional to force users to change their configs?
<maintainer> <email>i92guboj@gentoo.org</email> <description>Proxied committer, assign bugs</description> </maintainer> I guess the above (from metadata.xml) needs changing?
(In reply to comment #1) > <maintainer> > <email>i92guboj@gentoo.org</email> > <description>Proxied committer, assign bugs</description> > </maintainer> > > I guess the above (from metadata.xml) needs changing? > I can still test and bump the ebuild, and then give Jeremy Olexa a touch. That's what I always did (I have never ever committed an ebuild myself because I am just a forum staffer and not a proper developer. However, if there's someone else who's interested in fvwm and s/he is more active I will happily hand him/her the proxy maintainership (mostly because these days I've completely lost my interest for fvwm). About the above thing, I seem to recall something about that. fvwm doesn't ship an fv2m2 (now for a long time) script/link/whatever. That was an invention in the ebuild and it was dropped around 2002 (quite a long time ago as well) attending at the fvwm ebuild Changelog.
(In reply to comment #2) > About the above thing, I seem to recall something about that. fvwm doesn't ship > an fv2m2 (now for a long time) script/link/whatever. That was an invention in > the ebuild and it was dropped around 2002 (quite a long time ago as well) > attending at the fvwm ebuild Changelog. That's weird. I had several fvwm upgrades meanwhile and yes, I use Gentoo since about 2002. However, I probably once or twice re-installed from scratch ... I have emptied emerge.log soem time ago, but still here are the fvwm ebuods In had installed since that time: x11-wm/fvwm-2.5.25, x11-wm/fvwm-2.5.26, x11-wm/fvwm-2.5.27, x11-wm/fvwm-2.5.27-r1, x11-wm/fvwm-2.5.28, x11-wm/fvwm-2.5.30, x11-wm/fvwm-2.5.31 Why do I face the problem so late? >
(In reply to comment #3) > (In reply to comment #2) > > > About the above thing, I seem to recall something about that. fvwm doesn't ship > > an fv2m2 (now for a long time) script/link/whatever. That was an invention in > > the ebuild and it was dropped around 2002 (quite a long time ago as well) > > attending at the fvwm ebuild Changelog. > > That's weird. I had several fvwm upgrades meanwhile and yes, I use Gentoo since > about 2002. However, I probably once or twice re-installed from scratch ... > I have emptied emerge.log soem time ago, but still here are the fvwm ebuods In > had installed since that time: > > x11-wm/fvwm-2.5.25, x11-wm/fvwm-2.5.26, x11-wm/fvwm-2.5.27, > x11-wm/fvwm-2.5.27-r1, x11-wm/fvwm-2.5.28, x11-wm/fvwm-2.5.30, > x11-wm/fvwm-2.5.31 > > Why do I face the problem so late? I can't answer that because it's not been that long that I have been proxy-maintaining the ebuild. Probably Tavis Ormandy would be the one to answer that question (not sure). Assuming that the info in the ebuild is accurate (and again, I can't ever guarantee that), there could be a number of reasons why fvwm2 still worked in your system: * a remaining symlink not installed by portage residing somewhere in $PATH * a remaining custom script not installed by portage residing somewhere in $PATH * some function/alias in your shell rc files * ebuilds from an overlay, either locally managed or managed via layman * sabayon or the like However it's not really a big deal. If you don't want to change your xinitrc just use one of the "solutions" I listed above in this post. Obviously, if there's no fvwm2 script included in the upstream package I don't think it's Gentoo's duty to fabricate one.
(In reply to comment #4) > Obviously, if > there's no fvwm2 script included in the upstream package I don't think it's > Gentoo's duty to fabricate one. Agreed.
