/dev/rob0 wrote:
On Fri, May 28, 2010 at 09:51:07PM -0300, Niels Horn wrote:
<snip>

1) run -current in a Virtual Machine

or

2) maintain clean stable Virtual Machines

A virtual machine is overkill, generally. A chroot works well.
These are my bind-mounts:

cd /home/slackware-13.1 # where I have done a full install using
                         # installpkg -root /home/slackware-13.1
for MOUNT in proc proc/bus/usb sys tmp home ; do mount -v --bind \
/$MOUNT $MOUNT ; done
chroot .

You might not want/need /tmp and /home in that list, but I do. The
whole mess could be scripted with proper environment variables and
everything.

My main computer has an aging slamd64 install with a shiny newish
kernel. I'm using it to build some packages for my 32-bit netbook
which is running 13.1. In some cases there could be obscure bugs
occurring from the different kernels (I have a custom 2.6.31 rather
than a stock 13.1 kernel on here), but that's not likely, and
something that the SBo review process would probably find, if you
submitted a build tested in such a chroot.


au contraire mon fraire,

That virtual machine setup is ideal for package building/testing.

of course your setup is very nice also :)

--pw
_______________________________________________
SlackBuilds-users mailing list
[email protected]
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - http://slackbuilds.org/faq/

Reply via email to