http://www.osnews.com/story/17559/Creating_OpenBSD_Binary_Patches_in_a_Chroot_Environment Exploring the Future of Computing en-us Copyright 2001-2013, David Adams adam+nospam@osnews.com Thu, 23 May 2013 18:11:34 GMT http://www.osnews.com/images/osnews.gif http://www.osnews.com http://www.osnews.com/thread?224755 http://www.osnews.com/thread?224755 Of course, you could just do this:

1)Create a patch dir (say /usr/patches)
2) patch src and build for each affected system
3) env DESTDIR=/usr/patches make install
4) tar up the files and apply to other system

much easier, IMHO. Mon, 26 Mar 2007 18:05:00 GMT donotreply@osnews.com (Archite) Comments http://www.osnews.com/thread?224765 http://www.osnews.com/thread?224765 Thanks for your feedback. I thought about that as well, but the OpenBSD Makefile system may not always obey the DESTDIR approach, especially for those programs using the Makefile.bsd-wrapper file, like Apache. Mon, 26 Mar 2007 18:33:00 GMT donotreply@osnews.com (lteo_calyptix) Comments http://www.osnews.com/thread?224768 http://www.osnews.com/thread?224768 Yes, I have experienced that as well. In order to get around that you must play with other env variables. It's only a few and you can do it on a case by case basis. Some of them also panic if the file system is not laid out properly so I usually use mtree to rebuild the structure and then after installing patches remove empty directories. Mon, 26 Mar 2007 18:41:00 GMT donotreply@osnews.com (Archite) Comments http://www.osnews.com/thread?224794 http://www.osnews.com/thread?224794 My intent was to avoid Makefile environment variables and be as clean and consistent as possible with each patch -- hence, chroot. Thanks again for your insight. Mon, 26 Mar 2007 20:42:00 GMT donotreply@osnews.com (lteo_calyptix) Comments