LinuxQuestions.org
Share your knowledge at the LQ Wiki.
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 04-25-2005, 03:05 AM   #1
mozetti
Member
 
Registered: Jun 2004
Location: Germany
Distribution: Slack 10.1
Posts: 37

Rep: Reputation: 15
Software - Source or Package?


Hello slackers,

I'm new to linux and chose Slack because I wanted a distro that would force me to learn Linux and wasn't crippled by tons of bells & whistles (aka Suse 9.x). In that vein, I decided to only install software by compiling the source myself and installing it old school style without packaging, whenever possible. But, then I lose the nice features for dependencies and uninstallation that the packaging programs offer.

Compile from source without packaging, compile from source and package, or download packages? So, what are your opinions/methods and why?
 
Old 04-25-2005, 03:14 AM   #2
xushi
Senior Member
 
Registered: Jun 2003
Location: UK
Distribution: Gentoo
Posts: 1,288

Rep: Reputation: 45
Download package from slackware.com/pb
If its not there, then from linuxpackages.net

if its not there, then compile form source making package with checkinstall.

why? coz its easier, its there, and its good.
 
Old 04-25-2005, 03:15 AM   #3
reddazz
LQ Guru
 
Registered: Nov 2003
Location: N. E. England
Distribution: Fedora, CentOS, Debian
Posts: 16,298

Rep: Reputation: 77
On Slack you can install using source packages or create slackware packages using checkinstall. Most people prefer using checkinstall to make Slackware packages from source, because this makes them easier to remove or upgrade later on.
 
Old 04-25-2005, 04:13 AM   #4
uselpa
Senior Member
 
Registered: Oct 2004
Location: Luxemburg
Distribution: Slackware, OS X
Posts: 1,507

Rep: Reputation: 47
I guess the bottom line is to always use packages (-> easier uninstall). Use those which are available, and if somehing isn't, create your own package.
 
Old 04-25-2005, 05:17 AM   #5
mozetti
Member
 
Registered: Jun 2004
Location: Germany
Distribution: Slack 10.1
Posts: 37

Original Poster
Rep: Reputation: 15
As a follow-up:

Would a self-made package compiled from source and built by hand be "cleaner" or better optimized for my setup than a pre-made package from Slack?
 
Old 04-25-2005, 05:30 AM   #6
Nobber
Member
 
Registered: Jun 2002
Location: Nova Scotia
Distribution: Debian (home), Kubuntu 7.04 (work)
Posts: 265

Rep: Reputation: 30
Quote:
Originally posted by mozetti
Would a self-made package compiled from source and built by hand be "cleaner" or better optimized for my setup than a pre-made package from Slack?
That depends on how you compile it.

So: not necessarily, but if you know what you're doing, it could be.
 
Old 04-25-2005, 05:34 AM   #7
theYinYeti
Senior Member
 
Registered: Jul 2004
Location: France
Distribution: Arch Linux
Posts: 1,897

Rep: Reputation: 66
In case you're interested, I wrote a small article about this topic:
http://yves.gablin.club.fr/pc/linux....ftware/install

Yves.
 
Old 04-25-2005, 05:37 AM   #8
xushi
Senior Member
 
Registered: Jun 2003
Location: UK
Distribution: Gentoo
Posts: 1,288

Rep: Reputation: 45
Quote:
Originally posted by mozetti
As a follow-up:

Would a self-made package compiled from source and built by hand be "cleaner" or better optimized for my setup than a pre-made package from Slack?
Like Nobber said, it depends.. If you're using a different architecture, then yes. But if you're on a x86 cpu, then its the same thing, because most of the other packages are compiled with the same architecture.

If you, for example, were on an Athlon64 processor, then you would see a slight performance degredation.. but you can even find packages for athlon64 arc in LP.net nowadays..

So it all depends on how easy you want all this to be for you. If you want to go through the hassle of compiling, then be my guest, just try to use the program checkinstall so that it makes a package out of it.. If not for reinstalling, then for the ease of removing or upgrading the program later on..

This is alright for small programs like gaim, or ethereal.. but think twice about the hassle in compiling X or GCC for upgrading purposes... its a pain

So packages are a good idea.. I've been using Slackware's and LP.net's packages for years now, and i report no problems.
 
Old 04-25-2005, 06:39 AM   #9
dunric
Member
 
Registered: Jul 2004
Distribution: Void Linux, former Slackware
Posts: 498

Rep: Reputation: 100Reputation: 100
I don't intend to repeat previous suggestions but i'd highlight to never install software in any different way then from packages. If you need from various reasons to compile from sources, spend a bit time to create your own package instead of direct install. Slackware packages are very simple and very easy to create. Your system will stay clean and you can avoid many problems in future, if you keep this practice.
 
Old 04-25-2005, 10:03 AM   #10
freakyg
Member
 
Registered: Apr 2005
Distribution: LFS 5.0 and 6.1
Posts: 705

Rep: Reputation: 30
Quote:
Originally posted by dunric
I don't intend to repeat previous suggestions but i'd highlight to never install software in any different way then from packages.
Well sometimes you need to compile from source.............take an open source game like neverball/neverputt for example..........there are some people who offer tarballs of this game for Slackers, but the version is way behind.......1.28 or 1.32 neverball/neverputt is up to v.1.40 now .......so if we want the latest and greatest ...........we get the source and do it on our own...........

In fact this gives me an Idea............I'll get version 1.40 tarr'd and feather'd for the slackers here and post a link for all to download.......how's that??

Last edited by freakyg; 04-25-2005 at 10:07 AM.
 
Old 04-25-2005, 11:37 AM   #11
artistikone
Member
 
Registered: Jul 2003
Distribution: slackware-current
Posts: 76

Rep: Reputation: 15
My preference is to:

1. Install an official package from the tree.
2. Compile from source, use checkinstall for easy removal/upgrade.
 
Old 04-26-2005, 02:56 AM   #12
mozetti
Member
 
Registered: Jun 2004
Location: Germany
Distribution: Slack 10.1
Posts: 37

Original Poster
Rep: Reputation: 15
Great, thanks.

I think I'm going to go the route of compiling from source (w/ optimizations for arch, etc) when available, and making my own packages. After I get everything set up the way I want it and I learn a bit more about Linux/Slack, I'm going to re-compile a kernel w/ arch optimizations. Between the packages and the new kernel, it should be a good match.

Thanks for your advice!
 
Old 04-26-2005, 03:52 AM   #13
jschiwal
LQ Guru
 
Registered: Aug 2001
Location: Fargo, ND
Distribution: SuSE AMD64
Posts: 15,733

Rep: Reputation: 682Reputation: 682Reputation: 682Reputation: 682Reputation: 682Reputation: 682
Perhaps a compromise would be to install from a slackware source package if possible.

Looking at the output of 'configure --help' and reading the README and INSTALL files would enable you to learn about optional features that you might want to add by simply including an option with the ./configure command. One example would be including tcwrapper support for a service.

Last edited by jschiwal; 04-26-2005 at 03:58 AM.
 
Old 04-26-2005, 01:20 PM   #14
piete
Member
 
Registered: Apr 2005
Location: Havant, Hampshire, UK
Distribution: Slamd64, Slackware, PS2Linux
Posts: 465

Rep: Reputation: 44
I would echo the comments made by the previous posters and say that the heirarchy of installations goes along the lines of:

1. Check Slackware Package Browser. If the package exists, use it from there.

If it doesn't exist there ...

2. Go to linuxpackages.net and check there.

... and finally ...

3. Download, compile & "checkinstall"

I would add that I tend to skip step 2 because I've had some problems with linuxpackages.net and dependencies.

To add to Yves' site, you might consider investigating Application Directories (RiscOS / OSX styleee) as an alternative to packaging. Of course, an entire distro of app-dirs might be more than you want to deal with (I know I'm in no hurry to spend the time converting to them!). It makes interesting reading, tho' =)

http://rox.sourceforge.net/phpwiki/index.php/AppDir

I stress again: use this for reading and research, don't try and port your main box until you've got a test box to test it on!

- Piete.
 
  


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
Need Help: Free Software vs. Open Source Software General_Tso Linux - General 13 12-17-2005 09:49 PM
Wine Package or Source? Murdock1979 Linux - Software 1 07-03-2005 12:16 PM
Upgrading a package from source? thebudbottle Linux - Newbie 1 03-24-2005 03:58 PM
kernel-source package houston1981 DamnSmallLinux 0 12-01-2004 04:50 AM
compiling software from source...how do i delete the folder w/ source? webazoid Linux - Software 2 07-01-2004 09:09 PM

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

All times are GMT -5. The time now is 07:35 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
Open Source Consulting | Domain Registration