Icecream 1.0.1 was released on July 11, 2013.
SRC_URI is ftp://ftp.suse.com/pub/projects/icecream/icecc-1.0.1.tar.bz2
What a pity that I missed that. That was easy to refresh.
Ebuild is a copy of 1.0.0-r1, but I removed libcap-ng.patch as this was already fixed by suse.
Therefor I fixed the gentoo-init 'icecream-r2' as it hadn't respected the ICECREAM_ALLOW_REMOTE config option.
I ran some compile jobs in my mixed nix-cluster and this ebuild worked as normal.
Created attachment 407422 [details]
ebuild for icecream-1.0.1
Created attachment 407424 [details]
updated init file
It seems this new ebuild (like the latest one in tree) is also affected by:
and as such not used by emerge (unless a previous version was installed), can you confirm / fix this?
Thanks a lot!
Cannot confirm this in general. I cleaned up the old /usr/lib/icecc directory centurys ago by hand as my icecc stopped working - I'm sure the day as icecc-1.0.0 arrived.
But you're right. In my /usr/libexec/icecc/bin there were some leftovers from november 2013:
x86_64-pc-linux-gnu-c++ -> /usr/bin/icecc
x86_64-pc-linux-gnu-g++ -> /usr/bin/icecc
x86_64-pc-linux-gnu-gcc -> /usr/bin/icecc
I deleted them manually, restartet icecream and did some emerges, but these were still compiling fine in my icecc cluster.
I agree with you that it would be helpful to point the user to PREROOT etc and to include the symlinks from CHOST as in version 0.9.7.
Said this I renewed this ebuild and included an according patch to address this. Someone with ARCH other than x86/x86_64 should check that the symlinks of CHOST are set correctly.
(In reply to Oliver Freyermuth from comment #4)
> It seems this new ebuild (like the latest one in tree) is also affected by:
> and as such not used by emerge (unless a previous version was installed),
> can you confirm / fix this?
> Thanks a lot!
Created attachment 409716 [details]
Created attachment 409718 [details, diff]
patch to set CHOST symlinks
The ebuild in-tree now seems to use dev-util/shadowman for the links.
Also, icecream 1.1 has been released 8th August 2017.
See bug 642674.