> This has been considered before and we came to the conclusion > to simply stick to the -stable release. There is no reason > to have every single development version of software inside > the ports tree... unless there is a very good reason, but in > the case of fvwm2, I don't really see it. A stable release > will probably occur at some point soon, making these gymnastics > useless.
I totally agree about the uselessness of having 3 different possible versions of fvwm (the in-tree one, 2.4 and 2.5). The only thing is that, 2.5.18 doesn't break anything found in 2.4, I use it on i386 and amd64 (a homebrew port of mine). Its actually been really stable since its release, never crashed on me. The real reason I'd see for upgrading would be the EWMH compliance which is now complete, meaning that scripting through wmctrl works well now, I guess it must play ball better with desktop environments such as KDE but I don't use them. Anyway, they should just label it as stable, cause it is, this would solve the situation.
