|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
If you happen to be using OpenBSD, and think also that the default version of FVWM which comes with OpenBSD is supported, it isn't. Please use 2.6.X -- it should be in ports.
If you find any bugs, you can email the fvwm-workers mailing list.
If you just have a question, be sure to read our Documentation first, then you might want to try our Mailing List.
When asking for help, of course always remember to provide the release number of fvwm, your operating system, and any other information you think might be pertinent.
Don't use them. If you encounter a problem we will most likely ask you to upgrade. There is a constant stream of bug fixes and we cannot spend our time fixing the same bugs again and again.
Problems in one of the below packages should be discussed on the fvwm-workers Mailing List.If you want the development stuff but don't want to set up the build environment. Note that the snapshots may not even compile. Use them at your own risk.
When you must have the latest stuff, up to the minute, or want to contribute heavily. Please read the CVS instructions.
If you want to use CVS but can't. This directory is updated every three hours. It is simpler to use CVS than to fetch these files, but if you are behind a restrictive firewall or don't need CVS features like easy patch generation or commits then you can use an FTP mirroring tool to grab this directory. Since this is an exact copy of what you'd get if you did a CVS checkout, you should read up on CVS.
Last modified on June 04, 2011