LinuxQuestions.org
Download your favorite Linux distribution at LQ ISO.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 06-07-2010, 09:56 AM   #46
allend
LQ 5k Club
 
Registered: Oct 2003
Location: Melbourne
Distribution: Slackware-current
Posts: 5,203

Rep: Reputation: 1860Reputation: 1860Reputation: 1860Reputation: 1860Reputation: 1860Reputation: 1860Reputation: 1860Reputation: 1860Reputation: 1860Reputation: 1860Reputation: 1860

@darksaurian - No one. It is an old argument, and you come down on the side of your personal preference.
It is a bit like electric windows in cars. Some people find them a convenience and an improvement but they add to the complexity and introduce further points of failure. Other people like the old manual window window winders because they work, are easy to fine tune and are easier to fix, but require a little extra effort.
 
1 members found this post helpful.
Old 06-07-2010, 11:13 AM   #47
veeall
Member
 
Registered: May 2007
Location: Estonia
Distribution: Slackware64-current
Posts: 262

Rep: Reputation: 48
Personally, package dependencies are not obvious for me, for example if i build an mplayer package and later want to install it on another machine, i don't know what are the library dependencies for the given package, so i often just prefer to recompile it again. There are third party programs like depfinder, tracepkg, maybe some more. But i'd like to see that dependency information could be queried wiht an official tool - with slackpkg or something.

I know, i can point slapt-get/gslapt to salix or slacky repositories and have dependency resolution available. But this doesn't help much with packages compiled from slackbuilds. Also if slackware installations are not identical on different machines then README files from slackbuilds.org may not contain adequate info on required dependencies of an app.

Hardly a showstopping issue, but still sometimes bugs me a bit.
 
Old 06-08-2010, 04:32 PM   #48
Cultist
Member
 
Registered: Feb 2010
Location: Georgia
Distribution: Slackware64 14.2
Posts: 779

Original Poster
Rep: Reputation: 105Reputation: 105
wow, I started a war ^_^
 
Old 06-08-2010, 04:43 PM   #49
damgar
Senior Member
 
Registered: Sep 2009
Location: dallas, tx
Distribution: Slackware - current multilib/gsb Arch
Posts: 1,949
Blog Entries: 8

Rep: Reputation: 201Reputation: 201Reputation: 201
Quote:
Originally Posted by Cultist View Post
wow, I started a war ^_^
Welcome to Slackware! LOL!
 
Old 06-08-2010, 04:45 PM   #50
sycamorex
LQ Veteran
 
Registered: Nov 2005
Location: London
Distribution: Slackware64-current
Posts: 5,833
Blog Entries: 1

Rep: Reputation: 1229Reputation: 1229Reputation: 1229Reputation: 1229Reputation: 1229Reputation: 1229Reputation: 1229Reputation: 1229Reputation: 1229
Quote:
Originally Posted by Cultist View Post
wow, I started a war ^_^
Shame on you

I guess it's one of those vi-vs-emacs type of debate, LOL

Personally, I got used to manually handling dependencies and despite the fact that it can be tedious, I can see educational benefits of such a model.
 
Old 06-08-2010, 04:51 PM   #51
damgar
Senior Member
 
Registered: Sep 2009
Location: dallas, tx
Distribution: Slackware - current multilib/gsb Arch
Posts: 1,949
Blog Entries: 8

Rep: Reputation: 201Reputation: 201Reputation: 201
It may have been mentioned already, but slapt-get (which just uses Slackware's built in package management tools) does do dependency resolution. It works well enough, but with no large central repo it only goes so far. I just thought I'd mention it. Time to duck and cover now.
 
Old 06-08-2010, 04:54 PM   #52
Cultist
Member
 
Registered: Feb 2010
Location: Georgia
Distribution: Slackware64 14.2
Posts: 779

Original Poster
Rep: Reputation: 105Reputation: 105
Quote:
Originally Posted by damgar View Post
It may have been mentioned already, but slapt-get (which just uses Slackware's built in package management tools) does do dependency resolution. It works well enough, but with no large central repo it only goes so far. I just thought I'd mention it. Time to duck and cover now.
Yeah, thats one of the main things that convinced me to come over. Not that I don't mind doing my own dependency resolution, but I'd like something to back me up when I mess everything up trying to learn the regular Slackware way lol
 
Old 06-08-2010, 05:02 PM   #53
gapan
Member
 
Registered: Feb 2007
Posts: 370

Rep: Reputation: 142Reputation: 142
Keep in mind that slapt-get offers dependency resolution only with repositories that include dependency information, which is not the case with slackware repositories.
 
Old 06-08-2010, 05:03 PM   #54
damgar
Senior Member
 
Registered: Sep 2009
Location: dallas, tx
Distribution: Slackware - current multilib/gsb Arch
Posts: 1,949
Blog Entries: 8

Rep: Reputation: 201Reputation: 201Reputation: 201
Quote:
Originally Posted by Cultist View Post
Yeah, thats one of the main things that convinced me to come over. Not that I don't mind doing my own dependency resolution, but I'd like something to back me up when I mess everything up trying to learn the regular Slackware way lol
If you start with a full install (from another thread you don't look short on disk space!), then Slackbuilds.org will have 99% of what you want/need and they specify the dependencies and generally have them available as well. Once you get slackbuilds (it's worth your time to learn how to edit them) then SBopkg, if installed, will search for the slackbuilds, download the source, and install packages based on a queue so it just takes time to run. It's not (usually) the nightmare it's made out to be sometimes.

Last edited by damgar; 06-08-2010 at 05:05 PM.
 
Old 06-08-2010, 05:23 PM   #55
Cultist
Member
 
Registered: Feb 2010
Location: Georgia
Distribution: Slackware64 14.2
Posts: 779

Original Poster
Rep: Reputation: 105Reputation: 105
So, suppose I find PackageA.tar.gz on some random source site. I try to compile and install, but it requires packageB, packageC, packageD, and packageE as dependencies to work. Will it tell me this when I try to compile it, or will I have to dig around the site that I downloaded from and hope that it lists the required dependencies? Or can I just expect most tarballs to have dependencies listed inside? I've relied mostly on apt-get in Debian for my software, only compiled a few things and they've never required dependencies I didn't already have
 
Old 06-08-2010, 05:35 PM   #56
damgar
Senior Member
 
Registered: Sep 2009
Location: dallas, tx
Distribution: Slackware - current multilib/gsb Arch
Posts: 1,949
Blog Entries: 8

Rep: Reputation: 201Reputation: 201Reputation: 201
Quote:
Originally Posted by Cultist View Post
So, suppose I find PackageA.tar.gz on some random source site. I try to compile and install, but it requires packageB, packageC, packageD, and packageE as dependencies to work. Will it tell me this when I try to compile it, or will I have to dig around the site that I downloaded from and hope that it lists the required dependencies? Or can I just expect most tarballs to have dependencies listed inside? I've relied mostly on apt-get in Debian for my software, only compiled a few things and they've never required dependencies I didn't already have
Usually it will tell you that the build failed because libXYTJAH.so is missing or whatever. Not guaranteed. But as I said, slackbuilds.org is pretty extensive as is a full install of slackware.
 
Old 06-08-2010, 07:42 PM   #57
rkelsen
Senior Member
 
Registered: Sep 2004
Distribution: slackware
Posts: 2,219

Rep: Reputation: 546Reputation: 546Reputation: 546Reputation: 546Reputation: 546Reputation: 546
Hi Cultist, welcome aboard!

If you want to add software to your Slackware installation quickly and easily, I can highly recommend a little program called sbopkg.

It 'syncs' with the SlackBuilds website and lets you create queues of packages to install and builds & installs them for you. It also enables you to track updates for the packages it has built for you.

There are a couple of limitations with it: Firstly, it doesn't do automatic dependancy resolution, which, as you've already been made aware, is the "Slackware way." However, once you know what dependancies are required by a particular package, you can create an installation queue which will build things in the order you tell it. This requires a bit of research and planning, but sbopkg makes the rest of the job easy.

The second disadvantage is that your choices are limited to software in the SlackBuilds database, but the list is extensive and growing daily. It has all of my needs covered!

Enjoy!

P.S. To answer your question: Dependancy resolution is too complicated. This is Linux for slackers. We don't complicate things here.

Last edited by rkelsen; 06-08-2010 at 08:07 PM.
 
Old 06-08-2010, 08:13 PM   #58
zbreaker
Member
 
Registered: Dec 2008
Location: New York
Distribution: Slack -current, siduction
Posts: 253

Rep: Reputation: 29
Simple...Slackware...many packaging tools...but mind your own (minor) dependencies........
Like the philosophy.....great!
Want more automated tracking tools...Linux affords you many other avenues
 
Old 06-08-2010, 10:59 PM   #59
darksaurian
Member
 
Registered: Jun 2010
Location: USA
Distribution: Fedora Xfce spin
Posts: 201

Rep: Reputation: 27
I understand it like electric window vs. manual window but I don't know why anyone care. But on internet forum it all the time like, "You like electric window, you are a fool! I hate you!" all the time. I not understand. If someone want to use electric window what it have to do with me.
 
Old 06-09-2010, 07:56 AM   #60
damgar
Senior Member
 
Registered: Sep 2009
Location: dallas, tx
Distribution: Slackware - current multilib/gsb Arch
Posts: 1,949
Blog Entries: 8

Rep: Reputation: 201Reputation: 201Reputation: 201
Quote:
Originally Posted by darksaurian View Post
I understand it like electric window vs. manual window but I don't know why anyone care. But on internet forum it all the time like, "You like electric window, you are a fool! I hate you!" all the time. I not understand. If someone want to use electric window what it have to do with me.
LOL! I am one of those people that refuses to buy a car (truck actually because it's utilitarian) with electric windows. I also buy manual transmissions because when something goes wrong I can at least get the vehicle home! I guess Slackware was predestined for me!
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Package updater unable to resolve dependencies FC8 jayunplugged Fedora 2 03-07-2008 09:56 PM
Article about Slackware's 'Magic Package Maker( src2pkg) gnashley Slackware 22 12-01-2007 09:11 PM
LXer: A look at Slackware's package utilities LXer Syndicated Linux News 0 02-20-2007 11:46 PM
Poll: Yast Package Manager vs. Smart Package Manager in 10.1 agentchange SUSE / openSUSE 6 06-02-2006 08:29 AM
unsatisfied dependencies for smart package manager on PClinuxOS m.r.bob Linux - Distributions 5 01-16-2006 03:41 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 04:39 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration