Latest stable version of boinc is 5.4.9 which is compatible with all boinc projects. This version is incompatible with WorldCommunityGrid project, and the only resolution this time is downgrade to 5.4.9 which is not in the portage. My suggestion is to mask this version and force users to downgrade do latest stable version 5.4.9.
I will take a look at this when I get the chance, but could do with more help. Upstream don't seem to do proper source releases, it is not always very clear what the latest stable and beta versions are so I tend to do snapshots as and when I get time from CVS checkouts. If you can point me to more reliable information - some packagers mailing list perhaps? I would like to see them doing a source release for what they consider a stable version so I can just download that tarball and package it ideally. It would make keeping up with BOINC a lot easier, otherwise I could do with some more help maintaining the Gentoo ebuilds for it. Hopefully I will get more time to sit down with it soon but work pressures do not give me a great deal of free time. If anyone else in the sci herd fancies taking a look then please do. As this is just one project I would think those interested in that project could package.mask 5.5.6 locally? I could add an ewarn to the ebuild. I have other users asking for more recent versions for functionality they think they need...
On the site http://boinc.berkeley.edu/compile.php you got everything about compile process with dependecies repositories and so on. Stable release has revision tag=stable Example addres for stable release: http://setiathome.berkeley.edu/cgi-bin/cvsweb.cgi/boinc/?sortby=rev;logsort=rev;only_with_tag=stable an exerpt from http://boinc.berkeley.edu/source_code.php: Source code You can get the BOINC source code in two ways: * Access the CVS repository directly, e.g. with a command like cvs -d :pserver:anonymous:@alien.ssl.berkeley.edu:/home/cvs/cvsroot checkout boinc to get the development version, or cvs -d :pserver:anonymous:@alien.ssl.berkeley.edu:/home/cvs/cvsroot checkout -r stable boinc to get the stable version. * Browse the boinc or boinc_samples modules via a web-based interface. This is useful for getting individual files, or seeing the revision history. http://boinc.berkeley.edu/cgi-bin/cvsweb.cgi/boinc/ http://boinc.berkeley.edu/cgi-bin/cvsweb.cgi/boinc_samples/ At the moment i could not help you with providing ebuild but in near feature i suppose i could find some time for it. As i could propose solution for cvs dev versions. stop provide them as they are not compatible with all projects so they are unusable as i wrote before.
I have added 5.4.11 which is the latest stable tagged version as of today in CVS. I will be hard masking higher version numbers but I disagree with them being of no use. As time permits I will keep these up to date concentrating on the stable tagged version - poking me is permitted if they have been out for a few days without me noticing. Hopefully this version will work better for people, and those who want to use the latest beta can unmask it. I wish they would use a more transparent versioning scheme, release source tarballs for stable and may be announce their release. I am going to see if there is anything I can do with getting a small patch pushed I should have asked for ages ago. Thanks for pointing this out anyway. Hopefully this is a reasonable solution for everyone involved.
