2013/11/8 Dan HorĂ¡k <dan(a)danny.cz>:
On Fri, 8 Nov 2013 14:43:48 +0400
Peter Lemenkov <lemenkov(a)gmail.com> wrote:
> This will have an interesting consequence for the secondary
arches,
> such as s390/s390x and PowerPC. In the future all Erlang services in
> Fedora, namely CouchDB, Ejabberd, RabbitMQ, Riak, will *want* service
> written in golang (I wouldn't use word "*require*" here). Since golang
> is available only for x86/x86_64 and ARM, this could be an annoyance.
> Technically it will still be possible to run Erlang daemons on the
> secondary arches, but it will require some painful manual
> intervention, and lead to inevitable race conditions. Beware! Also I
> hope we'll see some progress on porting Golang on these achitectures.
Is there a strict dependency on golang or just on go? Because
"GCC
4.8.2 provides a complete implementation of the Go 1.1.2 release."
citing from gcc 4.8.2 release notes and we build gccgo on all our
secondary arches.
There won't be a *dependency*, just an additional highly desired
systemd-service. If no such service was found it will continue working
as it does right now. If this service is available then systemd starts
it, so Erlang-based application will benefit from it (this will
resolve some issues mysterious for the end users). Also I think of
adding something like this into Erlang spec-file:
%ifarch %{ix86} x86_64 %{arm}
Requires: eclus
%endif
As for eclus dependency on golang that's another interesting story.
Actually eclus doesn't require golang for building, and frankly
speaking I think we shouldn't require golang anywhere else for that -
instead we should come up with some kind of virtual provides for that.
I've built eclus with gcc-go and it works quite fine. In fact I'm
using exactly that build for a couple of weeks already w/o any issues.
However gcc-go doesn't improve situation with secondary arches:
http://thread.gmane.org/gmane.linux.redhat.fedora.golang/23
--
With best regards, Peter Lemenkov.