digikam 4.3.0 (was: depends_build on minimal version?)

René J.V. Bertin rjvbertin at gmail.com
Sat Sep 20 03:34:05 PDT 2014


On Saturday September 20 2014 11:20:04 Mojca Miklavec wrote:

So I uploaded a diff for my current version of the Portfile: https://trac.macports.org/ticket/45107 . The upstream bug report is here: https://bugs.kde.org/show_bug.cgi?id=339180

The trac ticket has a Portfile patch against the one currently in MacPorts. But if that one fails to install the port because of an ODBC or other issue my version for 4.3.0 might fail to install too ...

> > I'd love to figure out exactly what happens, but I'd need a hand from a seasoned cmake user for that. I find the syntax very unhelpful and it's not like this is a small and easy project to jump in and learn while doing.

> things, ...). To start with it complains about something I'm not
> familiar with: "Can't install libiodbc because conflicting ports are
> active: unixODBC"

*It* being what? I cannot recall having seen that error when I first installed a digikam port, but that was a while ago...

> (Ending with "Please consider dropping MacPorts in favor of homebrew,
> which is at least easier to deal with. Many people have dropped
> MacPorts because of problems such as the ones you are having.")

Heh... :-/

> On the contrary this is all very very confusing in CMake. And if you

Trust me, CMake is just confusing in a different way if you have never set up an autotools/autoconf/configure based project ...

> Se also https://trac.macports.org/ticket/42872

And probably any ticket that's due to having things installed in /usr/local ...

> The second line is wrong anyway. In particular we no longer ship CMake
> 2.8, but 3.0. The rest is (in my opinion) something that either the
> PortGroup should set or shouldn't (need to) be set at all.

I mentioned that in the upstream report, and Gilles replied that the portfile worked fine for him. Maybe cmake just ignores the line in question...

.


More information about the macports-users mailing list