Syncing multiple macport installs
Hello, Does anyone have any suggestions/recipes for keeping two macs in sync with regard to their macport installations? Specifically, is there a good way to build on one machine and then not have to duplicate that build process on the other? I tried changing the prefix and user/group of my macports install, in an attempt to localize it all within a single directory, but I have found that problematic (many ports do not play well in the sandbox). I've reverted to using the standard locations and owners, but I still worry about syncing two machines (say, with rsync or unison) since things are installed outside of /opt (eg. launch items, etc). As anyone built a system where you package up your macports as .pkg files and push them to other machines? (or something similar). Thanks in advance, -mark
On Dec 28, 2006, at 1:56 PM, Mark Fredrickson wrote:
Does anyone have any suggestions/recipes for keeping two macs in sync with regard to their macport installations? Specifically, is there a good way to build on one machine and then not have to duplicate that build process on the other?
You can turn on archive mode and share the archives across machines (and on the non-build machine run port in 'binary-only mode' with -b).
I tried changing the prefix and user/group of my macports install, in an attempt to localize it all within a single directory, but I have found that problematic (many ports do not play well in the sandbox).
I've reverted to using the standard locations and owners, but I still worry about syncing two machines (say, with rsync or unison) since things are installed outside of /opt (eg. launch items, etc).
As anyone built a system where you package up your macports as .pkg files and push them to other machines? (or something similar).
I've got an unfinished patch to let you pull archives from a remote repo, and have used it successfully on two machines I have access to (I just made the archives available via http and then I didn't have to rsync or otherwise mirror the archives from one machine to the other). -- Daniel J. Luke +========================================================+ | *---------------- dluke@geeklair.net ----------------* | | *-------------- http://www.geeklair.net -------------* | +========================================================+ | Opinions expressed are mine and do not necessarily | | reflect the opinions of my employer. | +========================================================+
On 12/28/06, Daniel J. Luke <dluke@geeklair.net> wrote:
On Dec 28, 2006, at 1:56 PM, Mark Fredrickson wrote:
Does anyone have any suggestions/recipes for keeping two macs in sync with regard to their macport installations? Specifically, is there a good way to build on one machine and then not have to duplicate that build process on the other?
You can turn on archive mode and share the archives across machines (and on the non-build machine run port in 'binary-only mode' with -b).
If anyone is interested, this method works very well. I actually turned on archive mode on both machines. In /opt/local/etc/ports/port.conf: 23 # Create and use binary archive packages for installation/reinstallation ease 24 portarchivemode yes I built the unison port on both machines and set up a sync process so that they can exchange binaries. (This is helpful if I decide to start building port X on my mini in the morning and later in the day I build port Y on the macbook. When I sync after work, I get both new archives on both machines). I still have to manually type "sudo port install package +variants" on the second machine, but just unpacking an archive is a lot faster than fetching, building, and installing the port from scratch. Cheers, -Mark
participants (2)
-
Daniel J. Luke
-
Mark Fredrickson