On Tue, May 31, 2011 at 07:04:10PM +0200, Glenn Moeller-Holst wrote: > At 22:17 +0200 29/05/11, Lukas-David Gorris wrote: > >Hello, > ... > >Not everybody will like the idea of using chroot. Personally I have been > >using org.openembedded.dev based environment for a long time and never > >needed it. > ... > >Best, > >Lukas > > > >_______________________________________________ > >Shr-devel mailing list > >Shr-devel@lists.shr-project.org > >http://lists.shr-project.org/mailman/listinfo/shr-devel > > Hi Lukas > > If want to use chroot for security reasons, you ought to look at:
the purpose of shr-chroot is to provide verified and shared environment for people who were building SHR and were experiencing build issues with OE which were caused by their bleeding/obsolete version of fedora/debian/ubuntu/gentoo/abc/xyz/your/favourite distro it allows us to reproduce build issue in most cases and then fix it in OE or update chroot env, but I never had issues in my gentoo installation which couldn't be solved in OE if someone knows about it and can reproduce it. So once again: it's not mandatory step to build SHR, if you have sane host installation and you can debug/fix issues nobody except you can see then use your distribution More information about why I started to use chroot myself (long before publishing it as shr-chroot) here: http://www.mail-archive.com/openembedded-devel@lists.openembedded.org/msg03765.html Xen/LXC/VirtualBox/whatever is of course also fine for such minimal system for OE builds, but main criteriums for me were performance, maintainability, easy to use and chroot won (at least for me) and since then many people asked me to share it, first as tarballed snapshosts, then integrating setup-shr-chroot/update-shr-chroot to our Makefile.. Cheers, -- Martin 'JaMa' Jansa jabber: martin.ja...@gmail.com
pgp0k9fybavGZ.pgp
Description: PGP signature
_______________________________________________ Shr-devel mailing list Shr-devel@lists.shr-project.org http://lists.shr-project.org/mailman/listinfo/shr-devel
