MacPorts on multiple Macs
Hi Petra, Regarding your question Do not do that I currently manage 15 computers with MacPorts installed and I can tell you that each machine is a universe on its own. Even those who are 'identical' at the hardware and software level they are not really absolutely equivalent and that depends on the software installed. In the past I tried simplifying my life by designing strategies to keep all 'identical' machines in sync, but it did not really work. I observed very erratic and unexplained behaviors. The way I 'solved' those problems is by installing everything locally on each machine and letting each box compile its software Even little details like the order you created the users on the machines can have drastic consequences for the assigned UIDs the system gives each user and that can result in all kinds of unexpected permission problems. Software updates by Apple could also change according to the software installed on each machine from machine to machine in ways we cannot really know in advance Simplify My two cents --R ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: MacPorts on multiple Macs
On Oct 13, 2012, at 02:34, Rodolfo Aramayo wrote: Hi Petra, Regarding your question Do not do that I currently manage 15 computers with MacPorts installed and I can tell you that each machine is a universe on its own. Even those who are 'identical' at the hardware and software level they are not really absolutely equivalent and that depends on the software installed. In the past I tried simplifying my life by designing strategies to keep all 'identical' machines in sync, but it did not really work. I observed very erratic and unexplained behaviors. The way I 'solved' those problems is by installing everything locally on each machine and letting each box compile its software Even little details like the order you created the users on the machines can have drastic consequences for the assigned UIDs the system gives each user and that can result in all kinds of unexpected permission problems. Software updates by Apple could also change according to the software installed on each machine from machine to machine in ways we cannot really know in advance But... we have buildbots now. They build binaries and distribute them to users. Many users are using this successfully. Yes, there have been occasional problems with this too... But since this is a feature we're committed to continuing to provide, we'd like to resolve any such problems. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: MacPorts on multiple Macs
Ryan, Buildbots are great and welcome and can produce binaries that can be reliable used in different machines of the same 'uname -m' architecture BUT MacPorts is more than that MacPorts does interact with directories outside '/opt/local' like the '/Users/Applications/MacPorts' And Macport cannot control UIDs which are locally assigned in most cases A 'normal' user who would just rsync directories within machines without taking, for example, UIDs into consideration can potentially inadvertently create all sorts of 'invisible' issues and although using the rsync parameter rsync --chmod=ugo=rwX which assigns the same UIDs to files as the target directory, could work, personally I have not tested this on 'live' MacPorts deployments Unfortunately we do do have ways to testing these 'protocols' without having to allocate significant amounts of resources AND time I wonder if virtualization could help..??? Thanks --R On Sat, Oct 13, 2012 at 3:57 AM, Ryan Schmidt ryandes...@macports.org wrote: On Oct 13, 2012, at 02:34, Rodolfo Aramayo wrote: Hi Petra, Regarding your question Do not do that I currently manage 15 computers with MacPorts installed and I can tell you that each machine is a universe on its own. Even those who are 'identical' at the hardware and software level they are not really absolutely equivalent and that depends on the software installed. In the past I tried simplifying my life by designing strategies to keep all 'identical' machines in sync, but it did not really work. I observed very erratic and unexplained behaviors. The way I 'solved' those problems is by installing everything locally on each machine and letting each box compile its software Even little details like the order you created the users on the machines can have drastic consequences for the assigned UIDs the system gives each user and that can result in all kinds of unexpected permission problems. Software updates by Apple could also change according to the software installed on each machine from machine to machine in ways we cannot really know in advance But... we have buildbots now. They build binaries and distribute them to users. Many users are using this successfully. Yes, there have been occasional problems with this too... But since this is a feature we're committed to continuing to provide, we'd like to resolve any such problems. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: MacPorts on multiple Macs
On Oct 13, 2012, at 10:10, Rodolfo Aramayo wrote: Buildbots are great and welcome and can produce binaries that can be reliable used in different machines of the same 'uname -m' architecture Our binaries are tagged with the architecture. Currently we only have binaries for x86_64. BUT MacPorts is more than that MacPorts does interact with directories outside '/opt/local' like the '/Users/Applications/MacPorts' The default applications_dir is /Applications/MacPorts (not /Users/Applications/MacPorts). If you've changed applications_dir (or prefix or frameworks_dir) from its default, then MacPorts will not try to use the pre-built binaries. And Macport cannot control UIDs which are locally assigned in most cases My understanding is that it should not matter if the UID of a particular user is different on your machine than it was on the buildbot machine. Things are matched up by username, not user ID. A 'normal' user who would just rsync directories within machines without taking, for example, UIDs into consideration can potentially inadvertently create all sorts of 'invisible' issues Ah yes now I see what you mean. I'm not familiar enough with rsync to be able to comment on that specifically but I can see how it would be a problem. Which reinforces the idea that you shouldn't try to be tricky and duplicate a MacPorts installation; instead you should install ports on each system as usual. and although using the rsync parameter rsync --chmod=ugo=rwX which assigns the same UIDs to files as the target directory, could work, personally I have not tested this on 'live' MacPorts deployments Unfortunately we do do have ways to testing these 'protocols' without having to allocate significant amounts of resources AND time I wonder if virtualization could help..??? ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: MacPorts on multiple Macs
On Sat, Oct 13, 2012 at 10:19 AM, Ryan Schmidt ryandes...@macports.org wrote: On Oct 13, 2012, at 10:10, Rodolfo Aramayo wrote: Buildbots are great and welcome and can produce binaries that can be reliable used in different machines of the same 'uname -m' architecture Our binaries are tagged with the architecture. Currently we only have binaries for x86_64. BUT MacPorts is more than that MacPorts does interact with directories outside '/opt/local' like the '/Users/Applications/MacPorts' The default applications_dir is /Applications/MacPorts (not /Users/Applications/MacPorts). If you've changed applications_dir (or prefix or frameworks_dir) from its default, then MacPorts will not try to use the pre-built binaries. My bad. I meant to say: '/Applications/MacPorts' And Macport cannot control UIDs which are locally assigned in most cases My understanding is that it should not matter if the UID of a particular user is different on your machine than it was on the buildbot machine. Things are matched up by username, not user ID. Which should work fine unless the user account is authenticated by a central server...But I guess that if the MacPorts user is created locally it should be OK A 'normal' user who would just rsync directories within machines without taking, for example, UIDs into consideration can potentially inadvertently create all sorts of 'invisible' issues Ah yes now I see what you mean. I'm not familiar enough with rsync to be able to comment on that specifically but I can see how it would be a problem. Which reinforces the idea that you shouldn't try to be tricky and duplicate a MacPorts installation; instead you should install ports on each system as usual. Amen to that...;;)) --R and although using the rsync parameter rsync --chmod=ugo=rwX which assigns the same UIDs to files as the target directory, could work, personally I have not tested this on 'live' MacPorts deployments Unfortunately we do do have ways to testing these 'protocols' without having to allocate significant amounts of resources AND time I wonder if virtualization could help..??? ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
MacPorts on multiple Macs
Hi, I would like to install MacPorts on multiple Macs (MacBook, iMac, ...) with Mountain Lion. I would copy the directory /opt/local to every Mac and the directories from the page http://guide.macports.org/#installing.macports.uninstalling also. Is this the right way? Or is there a more effective way to do this? Thank you very much. Petra smime.p7s Description: S/MIME cryptographic signature ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: MacPorts on multiple Macs
On Oct 12, 2012, at 04:12, Petra Humann hum...@tcs.inf.tu-dresden.de wrote: I would like to install MacPorts on multiple Macs (MacBook, iMac, ...) with Mountain Lion. I would copy the directory /opt/local to every Mac and the directories from the page http://guide.macports.org/#installing.macports.uninstalling also. Is this the right way? Or is there a more effective way to do this? I suppose there isn't a right way since MacPorts is not designed to be used like that. What you describe should work, but it would only be a one-time copy from machine A to B (C, D, etc.). If you later install additional software on A, you'd then have to install it separately on B (C, D, etc.). Unless you look into using rsync or something to sync them up. Now that we have pre-compiled binaries, there's less need for such things. Just install MacPorts separately on each machine and let it download the binaries. Unfortunately we don't have binaries for Mountain Lion yet. It seems to me like it should be possible to somehow instruct MacPorts to look for binaries that have already been installed on another local computer. I don't know how to do that though. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: MacPorts on multiple Macs
I suppose there isn't a right way since MacPorts is not designed to be used like that. What you describe should work, but it would only be a one-time copy from machine A to B (C, D, etc.). If you later install additional software on A, you'd then have to install it separately on B (C, D, etc.). Unless you look into using rsync or something to sync them up. It's roughly the same effort to copy a fresh installation than it is to run the installer on each machine, so why not do it the expected way? Now that we have pre-compiled binaries, there's less need for such things. Just install MacPorts separately on each machine and let it download the binaries. Unfortunately we don't have binaries for Mountain Lion yet. It seems to me like it should be possible to somehow instruct MacPorts to look for binaries that have already been installed on another local computer. I don't know how to do that though. You could setup a www server on one of the machines to offer up software available in /opt/local/var/macports/software, which is where the binary archives live. You then add that machine to /opt/local/etc/macports/archive_sites.conf Note that you'll need to setup a signing key for the packages. Some helpful instructions are available on the MacPorts site: https://trac.macports.org/wiki/howto/ShareArchives2 https://trac.macports.org/wiki/archives ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: MacPorts on multiple Macs
On Oct 12, 2012, at 2:12 AM, Petra Humann wrote: Hi, I would like to install MacPorts on multiple Macs (MacBook, iMac, ...) with Mountain Lion. I would copy the directory /opt/local to every Mac and the directories from the page http://guide.macports.org/#installing.macports.uninstalling also. Some ports create system users and groups that may not be created if only port activate is run. Regards, Bradley Giesbrecht (pixilla) smime.p7s Description: S/MIME cryptographic signature ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: MacPorts on multiple Macs
On Oct 12, 2012, at 09:44, Bradley Giesbrecht pixi...@macports.org wrote: Some ports create system users and groups that may not be created if only port activate is run. ...but those ports are broken and should be fixed (any invocations of the adduser and addgroup procedures should be replaced with the add_users option). File tickets if you find such ports. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
