there is the directions of how to install the mame system on lmce. Still a test thing, but works great. Please test and let me know of any issues with the install or TSCHAK with any problems.
Rule #1 - Be Patient - Rule #2 - Don't ask when, if you don't contribute - Rule #3 - You have coding skills - LinuxMCE's small brother is available: http://www.agocontrol.com
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
The idea of removing it completely, and just adding back those parts that are KNOWN to be correct sounds great to me.
The major problem is that people who FIND these wrong sections need to add to the wiki pointing out what is wrong. That wike is sooooo damn big that it would take months of several people's time to check every post in it for correctness. Some of the info has changed as the versions of kubuntu or the versions of linuxmce has changed. So what may be right today may be hosed tomorrow. Please anyone finding wrong documentation, ADD to the wiki saying what you found or why it is wrong. OR what hardware caused it to hose.
the irc channel is on irc.freenode.net the channel is #linuxmce
and like I said there is usually 40+ people in there round the clock, and the main developers stay in there most of the time along with some of us less skilled developer-wanna-bes answering questions.
Since 0710 is the version currently in development, does that mean that the code in the linuxmce.org SVN 0710 branch is the same as the code in the charonmedia.com SVN trunk?danielk and ender do much work to merge changes back to charonmedia from linuxmce. Charonmedia may miss the latest fixes from mantis.QuoteAnd what is the complete build procedure for that code? The simple procedure for getting and building the source tom_say posted in this thread was very tantalizing.the procedure for the 0710 branch is not for the faint hearted. Therefore we use the builder farm and nightly snapshots.
Daniel invested much time on the configure script and makefile in the charonmedia trunk. That nearly gives you the whole build. I suggest starting with that. You could pull missing pieces from the linuxmce trunk (e.g. mantis fixes) if you need any.
So if the files to be patched in the charonmedia.com SVN are identical to the ones in the linuxmce.org SVN, then working entirely against the charonmedia files is pretty safe. If the patch doesn't affect the code's API, it's even safer.
The problem could come if the new patch's effect collides with some function elsewhere in the code that's also been patched upstream in the callpath to the newly patched code. Like if the problem is that some data arrives in the wrong format at the code I'm patching, so I switch the data around depending on the bad format in the charonmedia.org SVN code, but meanwhile someone has patched some other code in the linuxmce.org SVN, so now the data doesn't actually arrive in that format anymore (but the charonmedia.org SVN code hasn't caught up to that patch yet). If there's no record of that other "upstream" patch being worked on in a Mantis bug report about what I'm patching. Still possible to collide, if someone isn't reporting in Mantis what they're patching and committing. But probably a very small risk.