#38240: Port request: Tiled ----------------------+-------------------------------- Reporter: egall@… | Owner: macports-tickets@… Type: request | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Resolution: | Keywords: Port: tiled | ----------------------+-------------------------------- Comment (by ryandesign@…): Replying to [ticket:38240 egall@…]:

{{{ license {BSD GPL-2 LGPLv2} }}}

The separator between license name and version should be "-" not "v".

{{{ # sourceforge project name is different from port name, so not using sourceforge fetch group master_sites http://sourceforge.net/projects/tiled/files/tiled- qt/${version}/ }}}

It looks the same. If it isn't, you use "sourceforce:projectname". Better yet, use the complete path within SourceForge as explained in wiki:howto/AvoidRedirects.

{{{ # Have to specify the .tar.gz dist because otherwise it might grab the .dmg binary # (note: haven't actually tested this; just speculating) distname ${name}-qt-${version}.tar.gz }}}

`distname` must be without suffix. To construct `distfiles`, `extract.suffix` is appended to each `distname`. There isn't any ambiguity about what MacPorts will do; it's quite straightforward.

(I did'''n't''' make this an attachment because it's incomplete and I do'''n't''' want anyone to try using it as an actual portfile as is)

If you could let us know what problems you encountered that might help us finish the port. -- Ticket URL: <https://trac.macports.org/ticket/38240#comment:1> MacPorts <http://www.macports.org/> Ports system for Mac OS

#38240: Port request: Tiled ----------------------+-------------------------------- Reporter: egall@… | Owner: macports-tickets@… Type: request | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Resolution: | Keywords: Port: tiled | ----------------------+-------------------------------- Comment (by ryandesign@…): Ah yes, this software configures using qmake. Yes unfortunately qmake seems to suck quite badly, or at least make it very difficult to be told how to use the archs and compilers we want it to, hence lots of jumping through hoops. Maybe a portgroup could alleviate some of the tedium. Someone who understands something about qmake would have to lead that effort. -- Ticket URL: <https://trac.macports.org/ticket/38240#comment:3> MacPorts <http://www.macports.org/> Ports system for Mac OS

#38240: Port request: Tiled ----------------------+-------------------------------- Reporter: egall@… | Owner: macports-tickets@… Type: request | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Resolution: fixed | Keywords: Port: tiled | ----------------------+-------------------------------- Changes (by ryandesign@…): * cc: ryandesign@… (added) * status: new => closed * resolution: => fixed Comment: Fixed and committed in r103590. (I just had to rip out all their Mac- specific packaging ideas which didn't seem ideal within the context of MacPorts.) -- Ticket URL: <https://trac.macports.org/ticket/38240#comment:5> MacPorts <http://www.macports.org/> Ports system for Mac OS

#38240: Port request: Tiled ----------------------+-------------------------------- Reporter: egall@… | Owner: macports-tickets@… Type: request | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Resolution: fixed | Keywords: Port: tiled | ----------------------+-------------------------------- Comment (by ryandesign@…): Yes but they're all patching the same thing. The developers were trying to be clever and put the libtiled library inside the tiled application bundle. This is desirable for standalone drag-and-drop installs, but that's not what MacPorts is, and users who want that can use the dylibbundler program. And it didn't quite make sense either, since they actually install three applications, but only the main tiled application contained the library; the other two apps were trying to use the library inside the main one. I think one of the settings in the cmake portgroup was interacting badly with the way they were setting the install_name. And also the install process was managing to install two copies of the library: one in the application bundle, and one in ${prefix}/lib. I decided to just stick with the one in ${prefix}/lib. -- Ticket URL: <https://trac.macports.org/ticket/38240#comment:7> MacPorts <http://www.macports.org/> Ports system for Mac OS