how to maintain multiple active versions of a port (e.g. octave)?

I am the developer of a Matlab/Octave package that I need to test against multiple versions of Matlab and Octave. I’ve been using MacPorts to build and install Octave on my system and was wondering what is the best way to … (1) keep older versions of a port when the port is updated to use a new

Re: how to maintain multiple active versions of a port (e.g. octave)?

On Sep 23, 2016, at 08:01, Ray Zimmerman wrote: > > I am the developer of a Matlab/Octave package that I need to test against > multiple versions of Matlab and Octave. I’ve been using MacPorts to build and > install Octave on my system and was wondering what is the best way to … > > (1) keep o

status of `pdftk' package

installation and upgrading of the pdftk package fails (and does so for some time) issuing: "pdftk currently does not build on OS X 10.11 or greater" any chance to see pdftk working again any time soon? or is it an upstream problem? thanks joerg -- Using Opera's revolutionary email client

Re: how to maintain multiple active versions of a port (e.g. octave)?

> On Sep 23, 2016, at 9:28 AM, Ryan Schmidt wrote: > > On Sep 23, 2016, at 08:01, Ray Zimmerman wrote: >> >> I am the developer of a Matlab/Octave package that I need to test against >> multiple versions of Matlab and Octave. I’ve been using MacPorts to build >> and install Octave on my syst

Re: status of `pdftk' package

On Sep 23, 2016, at 08:51, j. van den hoff wrote: > > installation and upgrading of the pdftk package fails (and does so for some > time) issuing: > > "pdftk currently does not build on OS X 10.11 or greater" > > any chance to see pdftk working again any time soon? or is it an upstream > prob

Re: how to maintain multiple active versions of a port (e.g. octave)?

> On Sep 23, 2016, at 09:04, Ray Zimmerman wrote: > >> To build a previous version of a port: >> >> https://trac.macports.org/wiki/howto/InstallingOlderPort >> >> You can have multiple versions of a port installed at the same time, but >> only one active and usable at a time. You can switch

A general upgrade question

I have two systems, an iMac and a Mac Mini. The iMac doesn’t do much - mostly aspell, and so my update to Sierra went quite smoothly. The Mac Mini on the other hand, is a bit more of a workhorse. Primarily acting as a web server. And, as I updated to Sierra, I discovered to my chagrin that I h

Re: A general upgrade question

Hi, I would suggest in your case, because your port list might be a little out of date, to not use the ./restore_ports.tcl scripts. Instead, manually look at your myports.txt and requested.txt files, decide which ports you still want and try install them one by one, with whatever variants you

Re: A general upgrade question

> On Sep 23, 2016, at 09:41, William H. Magill wrote: > > I have two systems, an iMac and a Mac Mini. > The iMac doesn’t do much - mostly aspell, and so my update to Sierra went > quite smoothly. > > The Mac Mini on the other hand, is a bit more of a workhorse. Primarily > acting as a web

Re: how to maintain multiple active versions of a port (e.g. octave)?

On Sep 23, 2016, at 10:09 AM, Ryan Schmidt wrote: > >> On Sep 23, 2016, at 09:04, Ray Zimmerman wrote: >> >>> To build a previous version of a port: >>> >>> https://trac.macports.org/wiki/howto/InstallingOlderPort >>> >>> You can have multiple versions of a port installed at the same time, bu

Re: how to maintain multiple active versions of a port (e.g. octave)?

One last question … can you give me a quick idea of how much work would be involved in me attempting to locally implement the first approach you mentioned (different ports for different versions of octave). That is, starting with the files for the 3.8.2 revision of the octave port, what would

Re: status of `pdftk' package

On Fri, 23 Sep 2016 16:06:16 +0200, Ryan Schmidt wrote: On Sep 23, 2016, at 08:51, j. van den hoff wrote: installation and upgrading of the pdftk package fails (and does so for some time) issuing: "pdftk currently does not build on OS X 10.11 or greater" any chance to see pdftk workin

Re: how to maintain multiple active versions of a port (e.g. octave)?

> > One last question … can you give me a quick idea of how much work would be > involved in me attempting to locally implement the first approach you > mentioned (different ports for different versions of octave). That is, > starting with the files for the 3.8.2 revision of the octave port, wh

osxfuse

Hello all, osxfuse does not build. I reinstalled macports after upgrading to 10.12.0. trying to build opencv, i get this: … :debug:build Executing org.macports.build (osxfuse) :debug:build Environment: CC_PRINT_OPTIONS='YES' CC_PRINT_OPTIONS_FILE='/opt/local/var/macports/build/_opt_local_var_

Re: osxfuse

On Fri, Sep 23, 2016 at 3:57 PM, Raoul MEGELAS wrote: > :info:build OSXFUSEBuildTool(): supported platforms: 10.11 If there is an upstream update for Sierra then you can file a ticket to update to it. If not, MacPorts cannot port the kernel module to the new kernel for you. -- bra

Re: osxfuse

On 2016-09-23, at 12:57 PM, Raoul MEGELAS wrote: > info:build OSXFUSEBuildTool(): building OSXFUSE kernel extension > and tools > :info:build xcrun: error: missing DEVELOPER_DIR path: > :info:build OSXFUSEBuildTool() failed: xcodebuild cannot build configuration > Release. Looks l

files in both kdepimlibs4 and gpgme

The following files seem to be part of both ports, which seems to require a forced activate, i.e. seems to be something that ideally shouldn't happen; yet they're not listed as incompatible/conflicting, to the contrary, gpgme is listed as a library dependency of kdepimlibs4. Seems like somethin

Re: files in both kdepimlibs4 and gpgme

On 9/23/16 4:25 PM, Richard L. Hamilton wrote: > The following files seem to be part of both ports, which seems to require a > forced activate, i.e. seems to be something that ideally shouldn't happen; > yet they're not listed as incompatible/conflicting, to the contrary, gpgme is > listed as a

Re: osxfuse

Thanks i will see that. Raoul > On 23 Sep 2016, at 22:05, Brandon Allbery wrote: > > > On Fri, Sep 23, 2016 at 3:57 PM, Raoul MEGELAS > wrote: > :info:build OSXFUSEBuildTool(): supported platforms: 10.11 > > If there is an upstream update for Sierra the

Re: osxfuse

> On 23 Sep 2016, at 22:12, Ken Cunningham > wrote: > > > On 2016-09-23, at 12:57 PM, Raoul MEGELAS wrote: > >> info:build OSXFUSEBuildTool(): building OSXFUSE kernel extension >> and tools >> :info:build xcrun: error: missing DEVELOPER_DIR path: >> :info:build OSXFUSEBuildTool(