Re: Packaging a compiled port to App
> On Feb 18, 2016, at 3:15 PM, Ryan Schmidt wrote: > > If what you are packaging is only an OS X application bundle, you can > consider instead using the dylibbundler port to make a distributable app that > can be drag-and-drop installed. On a similar note: is it possible to do this with the Spyder port (and place it in the Applications/macports folder)?___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Packaging a compiled port to App
On Thu, Feb 18, 2016 at 10:15 PM, Ryan Schmidt wrote: > For DIA… Please, *Dedicated Internet Access*? Thank you (and sorry). -- Eneko Gotzon Ares enekogot...@gmail.com ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Packaging a compiled port to App
> On Feb 18, 2016, at 3:13 PM, Alejandro Imass wrote: > > > > On Thu, Feb 18, 2016 at 2:48 PM, Ryan Schmidt wrote: > > > On Feb 17, 2016, at 1:35 PM, Alejandro Imass wrote: > > > > > > [...] > > > > > You want to use ‘port mdmg …’ or ‘port mpkg …’. Brief documentation at: > > > > https://guide.macports.org/#using.binaries.binary-packages > > > > [...] > > > This is awesome! Exactly what I was asking! > > Thanks !! > > But if you do this, make sure you are *not* using a MacPorts installation > whose prefix is /opt/local, because that will interfere with users who > already do have MacPorts installed, or those who may install it in the > future. Instead, build MacPorts from source in a different prefix, one chosen > specifically for the thing you are packaging. For DIA, /opt/dia could be a > good choice. > > > > Sure thing. Got it! > > Thanks for the additional tip! If what you are packaging is only an OS X application bundle, you can consider instead using the dylibbundler port to make a distributable app that can be drag-and-drop installed. ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Packaging a compiled port to App
On Thu, Feb 18, 2016 at 2:48 PM, Ryan Schmidt wrote: > > > On Feb 17, 2016, at 1:35 PM, Alejandro Imass > wrote: > > > > > [...] > > > > You want to use ‘port mdmg …’ or ‘port mpkg …’. Brief documentation at: > > > > https://guide.macports.org/#using.binaries.binary-packages > > > [...] > > This is awesome! Exactly what I was asking! > > Thanks !! > > But if you do this, make sure you are *not* using a MacPorts installation > whose prefix is /opt/local, because that will interfere with users who > already do have MacPorts installed, or those who may install it in the > future. Instead, build MacPorts from source in a different prefix, one > chosen specifically for the thing you are packaging. For DIA, /opt/dia > could be a good choice. > > > Sure thing. Got it! Thanks for the additional tip! Best, Alex ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Packaging a compiled port to App
> On Feb 17, 2016, at 1:35 PM, Alejandro Imass wrote: > > > > On Wednesday, February 17, 2016, Craig Treleaven > wrote: > > On Feb 17, 2016, at 1:57 PM, Alejandro Imass wrote: > > > > Is it possible to package a compiled port into an OS X App for distribution > > inside a company for users that don't have MacPorts ? > > > > Specifically I'd like to package DIA and it's dependencies into an App that > > I can post on a company server and other team members can easily install. > > You want to use ‘port mdmg …’ or ‘port mpkg …’. Brief documentation at: > > https://guide.macports.org/#using.binaries.binary-packages > > Either of these will create a self-containted installer for whichever package > you need. No need to install MacPorts or Xcode. > > > This is awesome! Exactly what I was asking! > Thanks !! But if you do this, make sure you are *not* using a MacPorts installation whose prefix is /opt/local, because that will interfere with users who already do have MacPorts installed, or those who may install it in the future. Instead, build MacPorts from source in a different prefix, one chosen specifically for the thing you are packaging. For DIA, /opt/dia could be a good choice. ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Packaging a compiled port to App
On Wednesday, February 17, 2016, Craig Treleaven wrote: > > On Feb 17, 2016, at 1:57 PM, Alejandro Imass > wrote: > > > > Is it possible to package a compiled port into an OS X App for > distribution inside a company for users that don't have MacPorts ? > > > > Specifically I'd like to package DIA and it's dependencies into an App > that I can post on a company server and other team members can easily > install. > > You want to use ‘port mdmg …’ or ‘port mpkg …’. Brief documentation at: > > https://guide.macports.org/#using.binaries.binary-packages > > Either of these will create a self-containted installer for whichever > package you need. No need to install MacPorts or Xcode. > > This is awesome! Exactly what I was asking! Thanks !! Alex > Pro tip: if the target port, or any dependency, has any post-activate > steps, these will NOT be executed by the installer. You’ll have to create > a script or manual process to take such actions. Probably need such just > set an appropriate PATH. > > Craig ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Packaging a compiled port to App
> On Feb 17, 2016, at 1:57 PM, Alejandro Imass wrote: > > Is it possible to package a compiled port into an OS X App for distribution > inside a company for users that don't have MacPorts ? > > Specifically I'd like to package DIA and it's dependencies into an App that I > can post on a company server and other team members can easily install. You want to use ‘port mdmg …’ or ‘port mpkg …’. Brief documentation at: https://guide.macports.org/#using.binaries.binary-packages Either of these will create a self-containted installer for whichever package you need. No need to install MacPorts or Xcode. Pro tip: if the target port, or any dependency, has any post-activate steps, these will NOT be executed by the installer. You’ll have to create a script or manual process to take such actions. Probably need such just set an appropriate PATH. Craig ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users