You are using a development branch, which means it is totally unsupported and likely to be less stable than even a beta release, and probably, most of the time, the SVN trunk.
For release versions, the SVN pulls in menuselect from a different repository. You will need to do that manually. However, you may find that the the menuselect configuration files are a relatively later part of the development. If you didn’t fetch with SVN, try doing so. Try fetching a release version and switching to the development branch, although I can’t guarantee that that won’t clean out the external components, as well.
Basically, if you are working with such leading edge code, you need someone with strong Unix development skills on your team, as you will have made yourself into a developer.
You are more likely to get help on such leading edge code on the developer mailing list, but don’t expect to be supported on any other basis than as a field tester of pre-beta software.
Also, if you are doing anything unusual, you should use CentOS 5, as, although this doesn’t seem to be CentOS version releated, the fork may have been made before any CentOS 6 workarounds were added.
Don’t mean to hijack the thread, but can you explain a bit about the Centos 6 issues? I’ve seen it mentioned here before. I’m running 11 on Centos6 and haven’t had an issue that I know of, but I’d like to know about potential problems. Thanks!
Ok thanks. It built ok for me on Centos 6.3 64bit, just had to install a few packages that were not there on a default installation. All of them were in the official repos however and it went smoothly and seems to work fine. We now return to your regularly scheduled thread
