<cydork> what do you mean by all over net?
<cydork> and we can keep this on pm as it is off-topic
<Sp4rKy> yes of course
<Sp4rKy> thx ofr your help
<cydork> ya so what is the nature of your project
<Sp4rKy> i mean any people can connect on the server for help packagers
<Sp4rKy> i explain you :
<Sp4rKy> 1 server on the net
<Sp4rKy> packagers can connect over ssh on this server
<Sp4rKy> and running their building process
<Sp4rKy> and all packagers (and why not more users) can connect their pc on the server
<Sp4rKy> with a client
<Sp4rKy> and i would this client use the free resource avaible on the client for split compilation process
<Sp4rKy> understand ?
<Sp4rKy> i'm sorry if my english is bad, i'm french :|
<cydork> the problem is the compiling process..
<Sp4rKy> why ?
<cydork> mpi is definately out of question as it requires a local cluster.
<Sp4rKy> ok
<Sp4rKy> so between mosix and boinc
<cydork> well for compiling you need a similar enviorment. on all the comps and pbuilder does it via chrooting
<cydork> read mosix carefully it's also for a local clusters
<Sp4rKy> so client need install a pbuilder
<Sp4rKy> :/
<cydork> pbuilder is a package which creates a chroot for building packages which are optionally targetted at releases other than the currently installed release.
<Sp4rKy> yes
<cydork> so that's your main problem.
<cydork> the frameworks like boinc are used for computation where there is just a binary which needs to be run on the client.
<Sp4rKy> 'cause if a client create a chroot, data can't be uploaded on the server at the end of process
<cydork> like folding@home
<Sp4rKy> yes
<Sp4rKy> i know it
<cydork> yep..
<Sp4rKy> and do you have any idea about how can i do
<cydork> let me think ..
<Sp4rKy> of course :D
<cydork> well only think which i can think of is to split the process into 2 parts.
<cydork> compiling and and installing
<Sp4rKy> what do you mean by installing ?
<cydork> compiling can be done on distributed env.
<Sp4rKy> yes
<cydork> like distcc
<Sp4rKy> yep :)
<Sp4rKy> i've thought about it
<cydork> but chrooting is difficult to paralize ..
<Sp4rKy> yes
<cydork> and is not that important
<cydork> coz it wont take much resorces.
<Sp4rKy> yep
<Sp4rKy> so your idea is creating chroot on server , and only distribute compilation with software like distcc ?
<cydork> yep.
<cydork> that's what i can think of now :)
<Sp4rKy> it seems to be a good idea
<Sp4rKy> and how can i use distcc and not gcc/g++ ?
<Sp4rKy> just modify configure script in rules ?
<Sp4rKy> (or something like that)
<cydork> yes there is something like disthosts variable in which you can set the hostnames.
<Sp4rKy> ok
<cydork> but still i think it will also work better if you have a local cluster.
<Sp4rKy> yes
<Sp4rKy> but it's not the real purpose
<cydork> but still it can be modified to work on different machines i guess.
<Sp4rKy> because i want all (debian/ubuntu/linux) users can connect on server for "help" community
<Sp4rKy> k
<cydork> anyways distcc uses gcc at backend so it wont be a much problem.
<Sp4rKy> yes
<Sp4rKy> your idea seems good
<cydork> well i cant say much at this moment.
<cydork> but you can find me on debian most of the time..
<Sp4rKy> k
<Sp4rKy> i really thanks you for your help
<cydork> np :)
<Sp4rKy> i 'll come back on #debian when the project will be started
<cydork> sure..
<Sp4rKy> you've been a BIGGGGG help for me :D
<cydork> no problem at all..
<Sp4rKy> :)
<Sp4rKy> thx again :D
<Sp4rKy> good bye
<cydork> bye
<Sp4rKy> i have to sleep :|
<cydork> same here
<cydork> :)
<Sp4rKy> :D
<Sp4rKy> good night so
<cydork> after a smoke of course