LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (https://www.linuxquestions.org/questions/slackware-14/)
-   -   -current and Digikam (https://www.linuxquestions.org/questions/slackware-14/current-and-digikam-940134/)

gargamel 04-21-2012 12:07 PM

Thanks, I'll try that. By saying I should comment out two lines, you mean that the boos patch still should be applied, right? Or is NO patch required, at all, anymore? Then there would be three lines, as far as I can see... ;)

gargamel

willysr 04-21-2012 12:21 PM

Yes, my bad. It was three lines there..., but if you add the cd core and cd .. It would be like 5 lines :)
Yes, you can commented all those lines and it should be ok

tomtomjkw 04-21-2012 12:22 PM

Logn story short - try the SlackBuild below:

Code:

#!/bin/sh

# Slackware build script for digiKam

# Copyright 2007-2011  Frank Caraballo <fecaraballo{at}gmail{dot}com>
# All rights reserved.
#
# Redistribution and use of this script, with or without modification, is
# permitted provided that the following conditions are met:
#
# 1. Redistributions of this script must retain the above copyright
#    notice, this list of conditions and the following disclaimer.
#
# THIS SOFTWARE IS PROVIDED BY THE AUTHOR ''AS IS'' AND ANY EXPRESS OR IMPLIED
# WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
# MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO
# EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
# SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
# PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS;
# OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
# WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
# OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
# ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

PRGNAM=digikam
VERSION=${VERSION:-2.6.0-beta3}
BUILD=${BUILD:-1}
TAG=${TAG:-_SBo}

if [ -z "$ARCH" ]; then
  case "$( uname -m )" in
    i?86) ARCH=i486 ;;
    arm*) ARCH=arm ;;
      *) ARCH=$( uname -m ) ;;
  esac                                                                                                                                                       
fi                                                                                                                                                           
                                                                                                                                                             
CWD=$(pwd)                                                                                                                                                   
TMP=${TMP:-/tmp/SBo}                                                                                                                                         
PKG=$TMP/package-$PRGNAM                                                                                                                                     
OUTPUT=${OUTPUT:-/tmp}

if [ "$ARCH" = "i486" ]; then
  SLKCFLAGS="-O2 -march=i486 -mtune=i686"
elif [ "$ARCH" = "i686" ]; then
  SLKCFLAGS="-O2 -march=i686 -mtune=i686"
elif [ "$ARCH" = "x86_64" ]; then
  SLKCFLAGS="-O2 -fPIC"
else
  SLKCFLAGS="-O2"
fi

set -e

rm -rf $PKG
mkdir -p $TMP $PKG $OUTPUT
cd $TMP
rm -rf $PRGNAM-$VERSION
tar xvf $CWD/$PRGNAM-$VERSION.tar.?z*
cd $PRGNAM-$VERSION
chown -R root:root .
find . \
 \( -perm 777 -o -perm 775 -o -perm 711 -o -perm 555 -o -perm 511 \) \
 -exec chmod 755 {} \; -o \
 \( -perm 666 -o -perm 664 -o -perm 600 -o -perm 444 -o -perm 440 -o -perm 400 \) \
 -exec chmod 644 {} \;

mkdir -p build
cd build
  cmake \
    -DCMAKE_C_FLAGS_RELEASE:STRING="$SLKCFLAGS" \
    -DCMAKE_CXX_FLAGS_RELEASE:STRING="$SLKCFLAGS" \
    -DCMAKE_INSTALL_PREFIX=/usr \
    -DLIB_SUFFIX=$(kde4-config --libsuffix) \
    -DMAN_INSTALL_DIR=/usr/man \
    -DSYSCONF_INSTALL_DIR=/etc/kde \
    -DCMAKE_BUILD_TYPE=Release ..
  make
  make install DESTDIR=$PKG
cd ..

find $PKG | xargs file | grep -e "executable" -e "shared object" | grep ELF \
  | cut -f 1 -d : | xargs strip --strip-unneeded 2> /dev/null || true

find $PKG/usr/man -type f -exec gzip -9 {} \;
for i in $( find $PKG/usr/man -type l ) ; do ln -s $( readlink $i ).gz $i.gz ; rm $i ; done

mkdir -p $PKG/usr/doc/$PRGNAM-$VERSION
cp -a \
  NEWS README \
  $PKG/usr/doc/$PRGNAM-$VERSION
cat $CWD/$PRGNAM.SlackBuild > $PKG/usr/doc/$PRGNAM-$VERSION/$PRGNAM.SlackBuild

mkdir -p $PKG/install
cat $CWD/slack-desc > $PKG/install/slack-desc
cat $CWD/doinst.sh > $PKG/install/doinst.sh

cd $PKG
/sbin/makepkg -l y -c n $OUTPUT/$PRGNAM-$VERSION-$ARCH-$BUILD$TAG.${PKGTYPE:-tgz}


gargamel 04-21-2012 12:42 PM

Quote:

Originally Posted by willysr (Post 4659321)
Yes, my bad. It was three lines there..., but if you add the cd core and cd .. It would be like 5 lines :)
Yes, you can commented all those lines and it should be ok

;)

Success! Thanks again,

gargamel

gargamel 04-21-2012 07:04 PM

Quote:

Originally Posted by tomtomjkw (Post 4659322)
Logn story short - try the SlackBuild below:

Code:

#!/bin/sh

# Slackware build script for digiKam

# Copyright 2007-2011  Frank Caraballo <fecaraballo{at}gmail{dot}com>
# All rights reserved.
#
[...]

cd $PKG
/sbin/makepkg -l y -c n $OUTPUT/$PRGNAM-$VERSION-$ARCH-$BUILD$TAG.${PKGTYPE:-tgz}


Thanks, perfect!

gargamel

cwizardone 09-17-2012 04:37 AM

As an update, I'm current building digiKam 2.9.0, using the script provided by tomtomjkw in post 18, above.
Thank you.
:hattip:
However, to do so I had to build and install Qjson and OpenCV. OpenCV took about 30 minutes or so to build and at this point digikam is only 20% through the process so it looks like just those two will take well over an hour.
All of this just to get the kipi-plugins for Gwenview.
There has to be an simpler way to get the kipi-plugins that are suppose to be available for at least two other KDE applications. I tried the version 1.90 plugins and digiKam of the same version number, but the plugins didn't work with Gwenview, with or without digiKam 1.90 installed.

schultzter 09-18-2012 12:23 AM

I've been using willysr's scripts for digikam & dependencies, and I'm running 2.9 without any issues!

Hopefully he'll be able to contribute all his work to slackbuilds.org since it's a bit easier managing everything through sbopkg.

Thanks again!

willysr 09-18-2012 01:14 AM

digiKam has it's own maintainer in SBo which is Frank Caraballo and he will push updates when Slackware 14.0 gets released

cwizardone 09-18-2012 07:30 AM

Quote:

Originally Posted by schultzter (Post 4782960)
I've been using willysr's scripts for digikam & dependencies, and I'm running 2.9 without any issues!

Hopefully he'll be able to contribute all his work to slackbuilds.org since it's a bit easier managing everything through sbopkg.

Thanks again!

That is all well and good if you want digiKam, but what if a user just wants the kipi-plugsin for Gwenview or the one or two other KDE applications which can use them? Tying the kipi-plugins to digiKam forces one to built and install an application that, perhaps, a user doesn't want or need. It all sounds very redmondish....
Which, btw, reminds me that during the build of digiKam it was looking for nepomuk. I didn't notice if it was looking for the other two of the evil triplets. As I've said before, I would like to see a working, real world demonstration of how those three are an actual benefit to the end user.

tomtomjkw 09-18-2012 12:00 PM

@cwizardone

Perhaps it was easier for Digikam developers to maintain one monolithic package, don't see any redmond-style approach here;
I'm in the same situation as you - don't use Digikam, just the plugins, but I am far from questioning the developer's decision.

cwizardone 09-18-2012 04:16 PM

Quote:

Originally Posted by tomtomjkw (Post 4783452)
@cwizardone...I'm in the same situation as you - don't use Digikam, just the plugins, but I am far from questioning the developer's decision.

I stopped taking things on blind faith when I was a child, and I certainly wouldn't accept anything from the people over at KDE without question.
I was just using digiKam and it looks like they built the package around the plug-ins. Since we are being forced to install it to get the kipi-plugins, digiKam should be part of the standard KDE installation.

willysr 09-18-2012 07:12 PM

Well, it's part of the extragear actually just like k3b
But digikam has many dependencies, so that's probably why it isn't included in slackware by default

cwizardone 09-19-2012 02:35 AM

Extragear?
You won't get there from the main KDE site. I had to do a search for it to find it and it is hopelessly out of date:

http://extragear.kde.org/

But nice to know it is there, I guess.
:)

willysr 09-19-2012 04:27 AM

Yes, the activity of those projects are mainly in GIT, not in the public website :)


All times are GMT -5. The time now is 05:40 AM.