[SOLVED] Slackware frights keep boggling my mind, enlighten me please, if you are so kind.

Aquarius_Girl · 02-24-2011, 11:13 PM

I acquired the Slackware DVD 2 months back,
even found the way to create the tag files,
partitioned the hard disk long long back,
but haven't yet installed due to dependency piles.

are dependency graphs mentioned anywhere,
I skimmed through READMEs, but got nowhere,
installpkg doesn't hold my hand,
I know I am blind since I am missing some point.

Question: I need to install the kdiff3 and the svn, I would be downloading the slackbuilds from my office, but how am I supposed to know which other libraries are required by both of them, of course one way is to search their respective websites, but I would like to know whether Slackware has a feature which tells in advance which are the dependencies and in which order they should be installed?

and secondly I would also like to know whether you spend hours resolving the dependencies when in fact you have less time to learn the tool which you are supposed to install?

frankbell · 02-24-2011, 11:34 PM

Slackware believes that resolving dependencies is the responsibility of the user. It is the Slackware Way.

Do not let it frighten you. I started with Slackware, and the Slackware Way made me into a loyalist.

When you learn Slackware, you know what you are doing. If you run into something you don't know how to do, you will know that you can learn how to do it. That confidence is invaluable.

If you install from Slackbuilds, the Slackbuilds scripts generally resolve dependencies. Since the Slackbuild scripts are text files, you can open them in an editor and look at them and even edit them if you wish before you run them.

Many dependency issues can be avoided simply by installing Gnome. Slackware dependency problems often relate to Gnome libraries since Pat stopped shipping Gnome with Slackware.

The Gnome Slackbuild is probably the best choice for installing Gnome, since it is built specifically for Slackware and will not duplicate stuff that Slackware already includes.

http://gnomeslackbuild.org/

Otherwise, when you download a program in *.tar.gz, decompress it, and attempt to compile from sources, the make command will burp when dependencies are missing; the resulting error messages will tell you what libraries are needed.

Do not let Slackware intimidate you. It is nowhere near as difficult as folks who haven't taken the time to understand it like to make out. If it weren't for being too lazy to make the Broadcom wireless work, I'd have blown away the Ubuntu on this here laptop and replaced it with Slackware long ago.

dugan · 02-24-2011, 11:38 PM

You're really supposed to start with a full install. A full install includes svn. Most people choose to install third party packages like kdiff3 from SlackBuilds.org, which lists dependencies. If no dependencies are listed, then it means that they are all included in a default Slackware install.

And no, I don't spend hours resolving dependencies. If you're installing third party packages from SlackBuilds.org, then checking dependencies takes one glance per package.

Squall90 · 02-25-2011, 02:10 AM

Quote:

Originally Posted by Anisha Kaul

[...] but how am I supposed to know which other libraries are required by both of them, of course one way is to search their respective websites, but I would like to know whether Slackware has a feature which tells in advance which are the dependencies and in which order they should be installed?

One way is just to download and try and you'll see what's missing if there comes and error.

The other way is to gather informations about kdiff and you'll probably find something. I found something in the README.
Here's and excerpt.

Code:

Requirements & Installation
---------------------------

- for KDE4:
   From version 0.9.94 on KDiff3 supports KDE4.
   For installation on most distributions you usually also require these packages (names as on opensuse):
   - g++ (g++, version 3.4 or newer)
   - libqt4-devel (Qt4-libs, version 4.4.0 or newer)
   - libkde4-devel (KDE4 Header files and development libraries)
   - libkonq-devel (optional, needed for the kdiff3-plugin, if not installed 
                    then the contextmenu plugin for konqueror won't be built.)
   - cmake (>2.6, checks dependencies and creates the Makefiles appopriate for your system)

   Typically in a terminal (e.g. konsole) you cd into the kdiff3-directory and run these commands.

      mkdir release                                  # create sub directory
      cd release                                     # cd into that directory
      kde4-config --prefix                           # Find out your KDE4-directory and note the result
      cmake .. -DCMAKE_INSTALL_PREFIX=<KDE4-prefix>  # create Makefile, replace <KDE4-prefix> with the prior result
      make                                           # run make (compile and link)
      sudo make install                              # install as root user

   Now KDiff3 should be ready to use. Type "kdiff3" to start it.
   There should also be a entry in your KDE-start menu in "(Applications->)Development".

   For creating a debug version:
      mkdir debug
      cd debug
      kde4-config --prefix                           # Find out your KDE4-directory and note the result
      cmake .. -DCMAKE_INSTALL_PREFIX=<KDE4-prefix>  -DCMAKE_BUILD_TYPE=debugfull
      make
      sudo make install

   The <KDE4-prefix> depends on your distribution:
   The command "kde4-config --prefix" should tell you.
   - For opensuse 11 use "/usr".

- Building KDiff3 with Qt4-libs, but without KDE
    - for Linux/Un*x
    - for Windows
    - for Mac

   The version 0.9.94 requires Qt 4.4.0 or newer (from www.trolltech.com) for compilation. 

   You always need
      - kdiff3-0.9.94.tar.gz

      - for Un*x:    gcc, g++ with version >=3.4.2
                     Qt-X11-libraries

      - for Windows: Qt-win-libs
                     If you have the Qt4 commercial edition, then compile with Visual Studio.NET2003 or newer.
                     If you use the Qt4 open source edition, then you'll need MinGW.
                     I verified that compilation and debugging works with these packages (probably newer ones will also work):
                     - Use MinGW-5.1.4.exe or newer to install the following or newer:
                       - gcc-core-3.4.5-20060117-1.tar.gz
                       - binutils-2.17.50-20060824-1.tar.gz
                       - gcc-g++-3.4.5-20060117-1.tar.gz
                       - mingw-runtime-3.14.tar.gz
                       - mingw32-make-3.81-2.tar.gz
                       - w32api-3.11.tar.gz
                     - gdb-6.3-2.exe (for debugging)

      - for Mac:     gcc, g++ with version >=3.4.2
                     Qt-Mac-libraries
      - Optional: Qt Creator IDE: Development environment optimized for Qt (http://trolltech.com/developer/qt-creator)

  Build-instructions (Un*x):
    - Make sure your shell-variable QTDIR is correct and that 
      your path contains the Qt4-bin-directory.
    - cd into the directory kdiff3-0.9.94/src-QT4 and type
    - qmake kdiff3.pro
    - make (or "gmake" for GNU-Make)

  Build-instructions (Windows):
    - set QTDIR=<QT4-dir>         e.g.: c:\qt\4.4.1
      set "PATH=%QTDIR%\bin;%PATH%"
    - cd into the directory kdiff3-0.9.94\src-Qt4 and type
    - qmake kdiff3.pro
    - Either "nmake" for Visual Studio or "mingw32-make" depending on what you have.

  Debugging with MinGW under Windows:
    - Qt Creator worked very good as debugger frontend too!
    - Debugging without gdb on the console:
      - The qt-win-opensource-4.4.1-mingw.exe only installs release dlls. You will have to compile the
         debug dlls yourself. Enter the qt-4.4.1-directory and run "configure -debug" and then "mingw32-make".
      - cd into the directory kdiff3-0.9.94\src-Qt4
      - edit the file "Makefile.Debug" and in the LFLAGS replace "-Wl,-subsystem,windows" with "-Wl,-subsystem,console"
         (this is necessary so that gdb can send a break signal to the running program)
      - mingw32-make debug (create a debuggable executable)
      - gdb debug\kdiff3.exe
      - At the "(gdb)"-prompt type "run" and enter to start.
      - While the program runs you can't set breakpoints, first interrupt it with Ctrl-C.
      - Use "help" to find out about how to use gdb. (Important commands: run, break, backtrace, print, quit)
         Using break with c++-methods requires to specify the parameter types too. Breakpoints in constructors might not work.

  Building KDiff3 (Qt4) for Mac OSX (with Intel processor) as a universal binary (by Michael Schmidt)
    1) Install Qt/Mac 4.x with thread support, static libraries and universal flag.
       (For Qt4 run "configure -static"; only necessary if the final binary should not require shared Qt4-libs.)
    2) cd .../kdiff3-0.9.94/src-QT4
    3a) Create a makefile for kdiff3 by executing:
       qmake kdiff3.pro
    3b) optionally generate XCode-Project (for debugging purposes only) by executing:
       qmake -spec macx-xcode kdiff3.pro
    4) Execute:
       make
    5) After the build completes copy kdiff3 from the kdiff3-0.9.94/src-QT4 directory to
       /Applications

  Creating and installing the translation messages
    The po directory contains translations from the KDE-translation teams.
    If you use the Qt-only-version of KDiff3, then the installation described above 
    won't install translations automatically.
    To create and install the translations:
    0) Make sure /usr/lib/qt3/bin/msg2qm exists 
       (comes with qt3-devel-tools. [Yes, really Qt3. There is no Qt4 replacement yet.])
    1) cd .../kdiff3-0.9.95/po
    2) sh create_qm_files install    (asks for a super user password)
    Just to create the files in the po directory (as needed for the windows version): 
    2) sh create_qm_files local


(End of KDiff3 with Qt4-instructions)
------------------------------------------------------------------------

lumak · 02-25-2011, 02:17 AM

ldd will list all the library files a binary links against and where (if) it found it on your system.

If you are compiling something new, it will obviously tell you what it needs each time it fails. If the dependency comes with Slackware then make sure to run ldd on all the binaries in the package and check.

Keep in mind that this will not track run time dependencies.

However

There are some Slackware repositories that work with slapt-get to resolve dependencies.

Which ones, I'm not sure. I don't bother with such things because a Full install with Slackbuilds.org and Alien Bob's repository are more than enough to keep any of my machines happy. Until I get off my butt and build the super streamlined media server to free up an extra gig for video storage, I don't really care much. Probably wouldn't even in that case. Why are people so concerned about removing unneeded packages from Slackware?

XavierP · 02-25-2011, 07:57 AM

Moved: This thread is more suitable in Slackware and has been moved accordingly to help your thread/question get the exposure it deserves.

Slax-Dude · 02-27-2011, 01:16 PM

Quote:

Originally Posted by dugan

You're really supposed to start with a full install. A full install includes svn. Most people choose to install third party packages like kdiff3 from SlackBuilds.org, which lists dependencies. If no dependencies are listed, then it means that they are all included in a default Slackware install.

And no, I don't spend hours resolving dependencies. If you're installing third party packages from SlackBuilds.org, then checking dependencies takes one glance per package.

What he said

Also, I think this post will help you.

Please note that using tagfiles without understanding how to manualy resolve dependencies, is a mistake (IMHO).
You should realy start with a full install.

Aquarius_Girl · 03-24-2011, 11:17 AM

I am back again, thanks to all the responders of this thread for the encouraging and enlightening posts (that was needed). I realized that installing through tagfiles and then installing each and every requirement and resolving the dependencies would take me ages, I have taken your advice and have had a full install, and posting from Slackware 13.1.

I have still have some things to install (from slackbuilds) like qtcreator, vlc player, chm reader, kdiff, kdesvn, etc. and as they say the journey of a thousand miles begins with a single step!

I have to fix up that icon now.

Aquarius_Girl · 03-24-2011, 11:26 AM

Now it is seen

It is a relief!

brianL · 03-24-2011, 12:40 PM

Hope you have many years of Happy Slacking, Anisha.

Aquarius_Girl · 03-24-2011, 12:48 PM

Quote:

Originally Posted by brianL

Hope you have many years of Happy Slacking, Anisha.

Aah, thanks, at the same time I am saddened that those minimal slack install threads of mine won't be marked SOLVED soon! With the Fluxbox WM, the current setup is looking cool and loads up extremely fast. I had to go for the change, the Suse's Xfce used to take 45 seconds to load on my laptop

That's a pretext I think, since I anyway wanted to experience the "elite" OS.

You were absconding all this while?

Gerard Lally · 03-24-2011, 02:38 PM

Quote:

Originally Posted by lumak

Why are people so concerned about removing unneeded packages from Slackware?

It stands to reason that the less data a disk has to churn through as it operates the less wear and tear on that disk. For provisioning servers it makes a big difference in seek times not having to churn through a huge /usr partition.

Aquarius_Girl · 03-25-2011, 07:10 AM

Just now installed kchmviewer from the slackbuilds, so happy about it

(in office (Slackware in the VirtualBox))

I was worrying abou the dependency hell, but nothing happened, I hope this is not a mirage!

Squall90 · 03-25-2011, 07:13 AM

If there are dependencies, they are usually listed in the description on SlackBuilds (or, if you download e.g. packages from AlienBob, he puts a *.dep file in the folder; see: http://connie.slackware.com/~alien/s...486-2alien.dep).

brianL · 03-25-2011, 07:14 AM

Have you got sbopkg yet? If not, get it, it speeds things up/makes things easier if you have a few SlackBuilds to run.

http://sbopkg.org/