From: James <wireless@tampabay.rr.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: libsubversion error
Date: Wed, 25 Mar 2015 19:19:13 +0000 (UTC) [thread overview]
Message-ID: <loom.20150325T200810-295@post.gmane.org> (raw)
In-Reply-To: loom.20150325T194602-793@post.gmane.org
James <wireless <at> tampabay.rr.com> writes:
>
> Alec Ten Harmsel <alec <at> alectenharmsel.com> writes:
>
> > > dev-vcs/subversion or dev-vcs/hgsubversion
>
> > dev-vcs/subversion provides all the stuff that you're looking for.
>
> Correct_a_mun_do!
>
> Now it compiled with the python flag enabled. Keep your toes cross
> now that the java flag is enabled.....
Well it compiles with the java flag enabled. The next release of
mesos-0.23.0 will allow for dynamically allocated resources and multiple
simultaneous frameworks. This means that most codes that run multi thread on
your single system (workstation or server) will now run on the mesos
cluster. Surely there will be tweaking of the frameworks and configurations,
but pretty much most things should run without issue. Truely transparent
gentoo-clustering is very near, imho.
distcc is already running on mesos [1]
Cephfs-0.93 is in portage and I'm diligently trying to test running
of a variety of codes on cephfs so HDFS nor any of the legacy hadoop
baggage is not needed to build and use your own gentoo cluster via mesos.
Mesos-0.22.0 will be in BGO as soon as I clean up a few things.
Mesos-0.23.0 is a game changer, imho! [2]
enjoy!
James
[1] https://github.com/mesos/mesos-distcc
[2] http://craigwickesser.com/2015/03/mesos-022-release/
prev parent reply other threads:[~2015-03-25 19:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-25 16:55 [gentoo-user] libsubversion error James
2015-03-25 17:50 ` Alec Ten Harmsel
2015-03-25 18:47 ` [gentoo-user] " James
2015-03-25 19:19 ` James [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=loom.20150325T200810-295@post.gmane.org \
--to=wireless@tampabay.rr.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox