public inbox for gentoo-soc@lists.gentoo.org
 help / color / mirror / Atom feed
From: Luca Barbato <lu_zero@gentoo.org>
To: gentoo-soc@lists.gentoo.org
Subject: Re: [gentoo-soc] Project Proposal : GenCC for "Gentoo Community Compiling"
Date: Tue, 19 Feb 2013 02:20:31 +0100	[thread overview]
Message-ID: <5122D35F.6090707@gentoo.org> (raw)
In-Reply-To: <1361194187.18852.170.camel@Coffee>

On 18/02/13 14:29, Antoine Pinsard wrote:
> This is a very basic approach of the tool but I think it gives the main
> idea of the projet. I would like to have your opinion on whether it
> could be a gsoc project or not. And if it could, what backgrounds it
> would require. I think this is much more about networking and security
> than compiling (though it would require at least a basic knowledge of
> distcc).

You should study what had been done in the past (distcc, icecream etc)
and figure out what they are lacking and why nobody is using them on a
geographic network.

Then you have the problem of building a ring of trust strong enough.

And eventually you have to come to term with how compilers behave
differently depending on a number of situations.

Looks a quite good research project but I warn you not to expect quick
or easy results.

lu


  parent reply	other threads:[~2013-02-19  1:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-18 13:29 [gentoo-soc] Project Proposal : GenCC for "Gentoo Community Compiling" Antoine Pinsard
2013-02-18 14:03 ` Patrick Lauer
2013-02-18 14:41   ` Antoine Pinsard
2013-02-18 19:13   ` Rich Freeman
2013-02-18 22:52     ` Antoine Pinsard
2013-02-18 23:27       ` Rich Freeman
2013-02-19  0:55         ` Antoine Pinsard
2013-02-19  1:20 ` Luca Barbato [this message]
2013-02-19 21:10   ` Antoine Pinsard
2013-04-01 14:43   ` Donnie Berkholz
2013-04-01 15:30     ` Rich Freeman

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=5122D35F.6090707@gentoo.org \
    --to=lu_zero@gentoo.org \
    --cc=gentoo-soc@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