I would like to propose a new ebuild for boinc, a binary ebuild. By having a binary install of boinc, it identifies the machine as 32bit and will download the 32bit application of the project you are trying to connect to. This is important b/c there are only a couple of projects that support 64 bit. All the big ones only support 32bit. I have tested downloading the 32bit binary and running it with einstein, it works without any issues. But I don't know what 32bit libraries it needs. If i can be of more help, let me know.
So why don't you just compile it for x86 yourself, instead of requesting us to maintain redundant binary stuff?
1) I am sure this will benefit more then just me 2) It is easier to manage installs with default ebuilds 3) The purpose of portage and ebuilds is to compile the program and all it's dependencies. 4) There is no documentation how to compile 32 bit apps in 64 bit 5) Is it done for other applications, why not this I could go on, but I will stop here. And next time, instead of being rude, how about giving a useful response. I realize yall get a lot of ebuild request, but again, this would be beneficial to others besides me. And there isn't a need to compile it if it is binary, the Boinc project gives one out there, but then I - the user - has to keep up with updates, again which is what portage is for. If there is an easy way to compile 32 bit applications on a 64bit arch, then please let me know. The only way I saw on the gentoo docs is to set up a 32bit chroot, to me this is unreasonable to ask a user to do.
It would assist me, but maybe thats just because I'm useless at installing binary packages, and even when i do they still appear to go wrong. Currently every version of boinc is masked as in testing. Having a binary version would at least leave me with a version in portage which I could use.
Created attachment 120683 [details] boinc-bin-5.8.16.ebuild Attached ebuild for a boinc-bin package. Please note that the GUI does not work, I created bug #180316 for that.
The GUI works for me now, turned out to be a few broken symlinks. Two notes about the ebuild: 1) I'm not sure about the dependencies, I guess most libraries are statically linked into the executable and therefore not required separately. It could be it only depends on libc. 2) For now the filenames and paths are the same as for the regular boinc ebuild. I'm not sure if that is what you'd want ultimately, but it is trivial to fix.
Boinc 6.2.15 commited to the tre and now introduces bindist useflag which enables binary build.
