On Thu, 31 Jan 2013 10:32:47 +0100 Bertrand Jacquin
<be...@meleeweb.net> wrote:

> On 2013-01-30 21:57, David Seikel wrote:
> > On Wed, 30 Jan 2013 13:01:20 +0000 Tom Hacohen
> > <tom.haco...@samsung.com> wrote:
> >
> >> On 30/01/13 11:32, Bertrand Jacquin wrote:
> >> > Hi,
> >> >
> >> > For e5 buildbot/whatever we will need different OS and 
> >> architecture
> >> > to test. So if some volunteer are free to build some, we can 
> >> gladly
> >> > host them.
> >> >
> >> > Needed OS :
> >> >
> >> >   - Windows XP x86
> >> >   - Windows XP x86_64
> >> >   - Windows Vista x86_64
> >> >   - Windows 7 x86_64
> >> >   - Windows 8 x86_64
> >> >
> >> >   (maybe more declination are needed ?)
> >> >
> >> >   - Mac OS X Snow Leopard
> >> >   - Mac OS X Lion
> >> >   - Mac OS X Mountain Lion
> >> >
> >> >   - FreeBSD 8
> >> >   - FreeBSD 9
> >> >
> >> >   - NetBSD 4.0 (still supported)
> >> >   - NetBSD 6.0 (still supported)
> >> >   - NetBSD 6.0
> >> >
> >> >   - OpenBSD 5.2
> >> >
> >> >   - ?? Other, and maybe more declination on previous list
> >
> > Various versions of Linux as well, or did you leave them off coz you
> > don't need any help setting them up?
> 
> No, I just forget them. Yes, you need ARM, mips, mipsel, ppc, ppc64, 
> sparc ...
> 
> >> You can't run Mac OS in a vm.
> >
> > It's possible, and it used to be legal, but Apple changed their 
> > license
> > terms to make that illegal now.  Now it's only legal to run Mac OSX 
> > on
> > actual Apple branded hardware.  Even if you own the Apple hardware,
> > it's still illegal to run Mac OSX on a virtual machine on something
> > else.
> 
> Don't they apply a specific licensing for developers ?

Not that I know of.  I'll add it to me TODO to check on that, since I
want to have a MAC OSX VM image myself for open source development.

> > While on the subject, we got suitable licenses for the Windows vms?
> 
> We don't currently have.
> 
> >> I think it's too soon for this. We haven't really figured out our
> >> whole CI process. Lets have those VMs when all of that is sorted.
> >
> > I agree here, especially with the talk of moving from buildbot to
> > jenkins.  Let that settle, as it might change the requirements.
> 
> Well, that's not an immediate request. It's a long term build farm 
> design.
> 
> > A very minimal default install of the OS, followed by a script that 
> > can
> > install the rest of the build tools and build dependencies needed,
> > is what I do. That makes things easy to reconstruct each OS later.
> > It should even help when building variants for any specific OS if
> > the script has a bit of flexibility.
> 
> Also, we can easily do LVM snapshot the VM so we can rewind if 
> everything is br0ken.
> 
> > A lot of people say "just use ssh" for connecting to the systems to
> > automate the builds.  Now I don't know what buildbot and jenkins
> > use, so this part might not be needed to say.
> 
> Builbot use a daemon on the slave host, master send order to the
> slave to build that revision for that build chain. There is no use of
> SSH, all transfers and orders are passed via a clear channel on a
> specific TCP port.

That's cool then.  B-)

-- 
A big old stinking pile of genius that no one wants
coz there are too many silver coated monkeys in the world.

Attachment: signature.asc
Description: PGP signature

------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_jan
_______________________________________________
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel

Reply via email to