Opened 14 years ago

Closed 14 years ago

#22337 closed submission (fixed)

digikam-devel 1.0.0-beta5 Submission of portfile for the digikam beta version

Reported by: jgosmann (Jan Gosmann) Owned by: mf2k (Frank Schima)
Priority: Normal Milestone:
Component: ports Version:
Keywords: digikam, kde, image manipulation, photo management Cc: smgava@…, julien@…
Port: digikam-devel

Description (last modified by mf2k (Frank Schima))

I've created a portfile for the digikam 1.0.0-beta5 version (http://www.digikam.org/).

This port depends on another port (kipi-plugins) I've just submitted: ticket:22336 Though my digikam-devel port has a variant allowing it to be build without kipi-plugins, you probaly want to check the port in at the same time.

Attachments (4)

Portfile (1.1 KB) - added by jgosmann (Jan Gosmann) 14 years ago.
Portfile for digikam 1.0.0-beta6
Portfile.2 (1.1 KB) - added by julien@… 14 years ago.
Portfile for Digikam 1.0.0 rc
Portfile.3 (1.1 KB) - added by julien@… 14 years ago.
New version of the portfile for 1.0.0rc : add dependency on libgphoto2 and liblqr
Portfile.4 (1.2 KB) - added by jgosmann (Jan Gosmann) 14 years ago.

Download all attachments as: .zip

Change History (24)

Changed 14 years ago by jgosmann (Jan Gosmann)

Attachment: Portfile added

Portfile for digikam 1.0.0-beta6

comment:1 Changed 14 years ago by jgosmann (Jan Gosmann)

Updated the portfile for Digikam version 1.0.0-beta6. I also changed the naming of the no_kipi variant to the conventions.

comment:2 Changed 14 years ago by smgava@…

Cc: smgava@… added

Cc Me!

comment:3 Changed 14 years ago by smgava@…

hope this and kipi plugins get added soon... digikam 1.0.0 betas are _vastly_ superior to the 0.10 version already in ports...

comment:4 Changed 14 years ago by mf2k (Frank Schima)

Description: modified (diff)
Version: 1.8.1

comment:5 Changed 14 years ago by mf2k (Frank Schima)

I see the following error when I try to install this:

--->  Computing dependencies for digikam-devel
--->  Fetching digikam-devel
--->  Attempting to fetch digikam-1.0.0-beta6.tar.bz2 from http://voxel.dl.sourceforge.net/digikam
--->  Verifying checksum(s) for digikam-devel
--->  Extracting digikam-devel
--->  Configuring digikam-devel
Error: Target org.macports.configure returned: configure failure: shell command " cd "/opt/local/var/macports/build/_opt_mports_trunk_dports_kde_digikam-devel/work/build" && cmake -DCMAKE_INSTALL_PREFIX=/opt/local -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_COLOR_MAKEFILE=ON -DCMAKE_BUILD_TYPE=Release -DCMAKE_BUILD_WITH_INSTALL_RPATH=ON -DCMAKE_SYSTEM_PREFIX_PATH="/opt/local;/usr" -DQT_QMAKE_EXECUTABLE=/opt/local/libexec/qt4-mac/bin/qmake -Wno-dev -DBUILD_doc=OFF -DBUILD_SHARED_LIBS=ON -DBUNDLE_INSTALL_DIR=/Applications/MacPorts/KDE4 -DPHONON_INCLUDE_DIR=/opt/local/libexec/qt4-mac/include -DPHONON_LIBRARY=/opt/local/libexec/qt4-mac/lib/phonon.framework/phonon -DQT_QMAKE_EXECUTABLE=/opt/local/libexec/qt4-mac/bin/qmake -DKDE_DISTRIBUTION_TEXT="MacPorts/Mac OS X" ../digikam-1.0.0-beta6 " returned error 1
Command output:    used as include directory in directory /opt/local/var/macports/build/_opt_mports_trunk_dports_kde_digikam-devel/work/digikam-1.0.0-beta6/po/it
   used as include directory in directory /opt/local/var/macports/build/_opt_mports_trunk_dports_kde_digikam-devel/work/digikam-1.0.0-beta6/po/km
   used as include directory in directory /opt/local/var/macports/build/_opt_mports_trunk_dports_kde_digikam-devel/work/digikam-1.0.0-beta6/po/ko
   used as include directory in directory /opt/local/var/macports/build/_opt_mports_trunk_dports_kde_digikam-devel/work/digikam-1.0.0-beta6/po/lt
   used as include directory in directory /opt/local/var/macports/build/_opt_mports_trunk_dports_kde_digikam-devel/work/digikam-1.0.0-beta6/po/lv
   used as include directory in directory /opt/local/var/macports/build/_opt_mports_trunk_dports_kde_digikam-devel/work/digikam-1.0.0-beta6/po/nb
   used as include directory in directory /opt/local/var/macports/build/_opt_mports_trunk_dports_kde_digikam-devel/work/digikam-1.0.0-beta6/po/ne
   used as include directory in directory /opt/local/var/macports/build/_opt_mports_trunk_dports_kde_digikam-devel/work/digikam-1.0.0-beta6/po/nl
   used as include directory in directory /opt/local/var/macports/build/_opt_mports_trunk_dports_kde_digikam-devel/work/digikam-1.0.0-beta6/po/nn
   used as include directory in directory /opt/local/var/macports/build/_opt_mports_trunk_dports_kde_digikam-devel/work/digikam-1.0.0-beta6/po/pa
   used as include directory in directory /opt/local/var/macports/build/_opt_mports_trunk_dports_kde_digikam-devel/work/digikam-1.0.0-beta6/po/pl
   used as include directory in directory /opt/local/var/macports/build/_opt_mports_trunk_dports_kde_digikam-devel/work/digikam-1.0.0-beta6/po/pt
   used as include directory in directory /opt/local/var/macports/build/_opt_mports_trunk_dports_kde_digikam-devel/work/digikam-1.0.0-beta6/po/ro
   used as include directory in directory /opt/local/var/macports/build/_opt_mports_trunk_dports_kde_digikam-devel/work/digikam-1.0.0-beta6/po/se
   used as include directory in directory /opt/local/var/macports/build/_opt_mports_trunk_dports_kde_digikam-devel/work/digikam-1.0.0-beta6/po/ru
   used as include directory in directory /opt/local/var/macports/build/_opt_mports_trunk_dports_kde_digikam-devel/work/digikam-1.0.0-beta6/po/sk
   used as include directory in directory /opt/local/var/macports/build/_opt_mports_trunk_dports_kde_digikam-devel/work/digikam-1.0.0-beta6/po/sl
   used as include directory in directory /opt/local/var/macports/build/_opt_mports_trunk_dports_kde_digikam-devel/work/digikam-1.0.0-beta6/po/th
   used as include directory in directory /opt/local/var/macports/build/_opt_mports_trunk_dports_kde_digikam-devel/work/digikam-1.0.0-beta6/po/sv
   used as include directory in directory /opt/local/var/macports/build/_opt_mports_trunk_dports_kde_digikam-devel/work/digikam-1.0.0-beta6/po/tr
   used as include directory in directory /opt/local/var/macports/build/_opt_mports_trunk_dports_kde_digikam-devel/work/digikam-1.0.0-beta6/po/uk
   used as include directory in directory /opt/local/var/macports/build/_opt_mports_trunk_dports_kde_digikam-devel/work/digikam-1.0.0-beta6/po/vi
   used as include directory in directory /opt/local/var/macports/build/_opt_mports_trunk_dports_kde_digikam-devel/work/digikam-1.0.0-beta6/po/hne
   used as include directory in directory /opt/local/var/macports/build/_opt_mports_trunk_dports_kde_digikam-devel/work/digikam-1.0.0-beta6/po/nds
   used as include directory in directory /opt/local/var/macports/build/_opt_mports_trunk_dports_kde_digikam-devel/work/digikam-1.0.0-beta6/po/en_GB
   used as include directory in directory /opt/local/var/macports/build/_opt_mports_trunk_dports_kde_digikam-devel/work/digikam-1.0.0-beta6/po/pt_BR
   used as include directory in directory /opt/local/var/macports/build/_opt_mports_trunk_dports_kde_digikam-devel/work/digikam-1.0.0-beta6/po/zh_CN
   used as include directory in directory /opt/local/var/macports/build/_opt_mports_trunk_dports_kde_digikam-devel/work/digikam-1.0.0-beta6/po/zh_TW

-- Configuring incomplete, errors occurred!

Error: Status 1 encountered during processing.

comment:6 Changed 14 years ago by mf2k (Frank Schima)

Cc: macsforever2000@… added

Cc Me!

comment:7 Changed 14 years ago by jgosmann (Jan Gosmann)

I am not able to reproduce these errors. Using my portfile digikam configures just fine by me. Maybe I can test this port on another Mac.

Moreover the error is strange. I don't really know what the reason may be. By looking at the directories in the message, it might be a problem with gettext. Do you have the gettext package installed? But it would be surprising if not, because this port depends on kdelibs4 which depends on gettext.

Might it be that the port command does not display the full error message, but only a few lines of it?

comment:8 Changed 14 years ago by julien@…

Cc: julien@… added

Cc Me!

Changed 14 years ago by julien@…

Attachment: Portfile.2 added

Portfile for Digikam 1.0.0 rc

comment:9 in reply to:  5 Changed 14 years ago by julien@…

I can not reproduce these errors either. Here is what I did under MacOS 10.6.

make port install digikam -> it installs 0.10 version

then I downloaded the Portfile for 1.0.0 beta 6 -> all went fine

I updated the Portfile for 1.0.0 rc -> all went fine

Maybe the errors are due to missing dependencies in the portfiles for 1.0.0 ?

Julien

comment:10 Changed 14 years ago by julien@…

Do we really need to have those two dependencies ?

port:kdelibs4 \ port:kdebase4-runtime \

as

port:kdegraphics4 \

already depends on the two above.

Julien

Changed 14 years ago by julien@…

Attachment: Portfile.3 added

New version of the portfile for 1.0.0rc : add dependency on libgphoto2 and liblqr

comment:11 Changed 14 years ago by jgosmann (Jan Gosmann)

You are right, the two dependencies mentioned above are unnecessary.

libgphoto2 and liblqr are optional dependencies. But it is probably fine to get them installed.

I also checked the dependency list of Digikam and occured to me that also liblensfun and libmarblewidget are missing. Afaik there is no port for liblensfun and I wasn't able to compile under Mac. However, libmarblewidget should be included in the kdeedu4 port. We might also want to add that dependency.

One more remark to the no_kipi variant: In general it is not enough to remove the dependency, but you have also to set compiler flags excluding this dependency also if it is installed. But afaik you can install or uninstall kipi-plugins without recompiling it. I will check this again and if it is right the dependency should noted with the depends_run keyword.

I will try the updated portfile for 1.0.0rc myself soon. Whoever is quicker can do those changes.

Jan

comment:12 Changed 14 years ago by julien@…

Hi Jan,

I think you are right. You can have kipi-plugins installed without digikam and digikam without kipi-plugins and I think they both can be compiled independently. I think it is good thing that by default Digikam is shipped with kipi-plugins so adding depends_run should be the right think to do. For libmarblewidget, it would be better to depend on something smaller but if it is the only package which provides libmarblewidget ...

By the way, a bit off topic, but for kipi plugins, one need a browser for some plugins (flickr export , facebook export ...) , currently it does not open safari by default so maybe kipi-plugins should depends_run on konqueror ? I also tried to update PortFile for kipi-plugins to 0.9.0 but I don't know if we have to keep the patch of CMakelist.txt ?

Julien

comment:13 Changed 14 years ago by jgosmann (Jan Gosmann)

Is there any possibility to change the default browser used by the plugins? By me Konqueror is used, but displays only the HTML code (and does not render the website). I do not know whether it is useful to include konqueror in the dependencies as long as this problem persists.

I think the patch of CMakeList.txt can be removed. I reported that bug to the KDE developers, they fixed it and the SVN version compiled then fine for me. But to be sure, you (or I) should test it again with the 0.9.0 version.

Concerning libmarblewidget: I think kdeedu4 is the only package providing libmarblewidget. I also was not able to find just the source of libmarblewidget as download.

Jan

comment:14 Changed 14 years ago by julien@…

Jan,

For me, 0.9.0 compiles fine without the patch.

Let's put kdeedu4 as a dependency maybe put a comment to tell it is for libmarblewidget it is not obvious.

Maybe you should fill a bug about the konqueror issue I have not tried myself, I thought it would work with konqueror....

Julien

comment:15 Changed 14 years ago by jgosmann (Jan Gosmann)

I will attach an updated portfile.

The issue with konquerer I will further investigate as soon as I have time for it.

Jan

Changed 14 years ago by jgosmann (Jan Gosmann)

Attachment: Portfile.4 added

comment:16 Changed 14 years ago by julien@…

Portfile.4 compiles fine and runs fine for me. It would be nice to have this in the svn.

Julien

comment:17 Changed 14 years ago by julien@…

By the way name shoud be "digikam" instead of "digikam-devel" ...

Julien

comment:18 Changed 14 years ago by jgosmann (Jan Gosmann)

I would say it should be still digikam-devel, because it is not a stable version, yet.

Of course as soon as the version changes from release candidate to the stable 1.0.0 the port name should be changed to digikam.

Jan

comment:19 Changed 14 years ago by mf2k (Frank Schima)

Cc: macsforever2000@… removed
Owner: changed from macports-tickets@… to macsforever2000@…
Status: newassigned

comment:20 Changed 14 years ago by mf2k (Frank Schima)

Resolution: fixed
Status: assignedclosed

Added in r61186. Thanks!

Note: See TracTickets for help on using tickets.