[Bf-linux] Todo for 2nd test build. meeting notes

[Shaul Kedem]

Yes, I am referring to the releases. anyway, if it works for you then
great; somehow having an image for kvm/xen seems easier than
configuring one OS chroot env to another parent OS.

On Wed, Apr 9, 2008 at 9:24 PM, GSR <gsr.b3d at infernal-iceberg.com> wrote:
> Hi,
>  shaul.kedem at gmail.com (2008-04-09 at 1234.23 +0200):
>
> > On 4/8/08, GSR <gsr.b3d at infernal-iceberg.com> wrote:
>  > > Hi,
>  > > shaul.kedem at gmail.com (2008-04-08 at 2002.44 +0300):
>  > > > You talk about the cons, which is fine, but what about the pros?
>  > > > common arch that behaves like a full linux, place to test the build
>  > > > and not just deliver it, and so on.
>  > > The chroot does exactly that, it gives you a full user space of a
>  > > different distro. If the kernel below it is compatible, which should
>  > > be the case if you do not try mixing levels with big age differences,
>  > > there should be no problem. You can look all kind of tutorials in
>  > > which people build and test things mixing distros, run 32bit apps with
>  > > 64bit kernels, or even migrate from one distro to another by means of
>  > > chroots.
>  > I know all of that, the question is, how far the gap is? do you create
>  > an update chroot every time ?
>
>  What gap are you referring to? And every time "of what"? Blender
>  release? The chroot is self updating capable anyway.
>
>
>
>  GSR
>
>  _______________________________________________
>  Bf-linux mailing list
>  Bf-linux at blender.org
>  http://lists.blender.org/mailman/listinfo/bf-linux
>