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 12-03-2005, 06:49 AM   #1
Swift&Smart
Member
 
Registered: Jan 2003
Location: Hong Kong,China
Distribution: Slackware,OpenSUSE
Posts: 472

Rep: Reputation: 30
Prefer tgz or source file?


Hello,everyone.

I am wondering what do you guys prefer when installing software. Slackware package or source code from the official website? I would like to know because sometimes if you want some specific functions you have to compile from the source code with specific parameters which Slackware package may not be provided.

For example, I just can't figure out how to install MPlayer from Slackware package. I can't get it done.

If you guys have any ideas, please drop me a line.
 
Old 12-03-2005, 11:33 AM   #2
XavierP
Moderator
 
Registered: Nov 2002
Location: Kent, England
Distribution: Lubuntu
Posts: 19,176
Blog Entries: 4

Rep: Reputation: 430Reputation: 430Reputation: 430Reputation: 430Reputation: 430
MPlayer compiles and works best, in my experience, if you do it all from source.
 
Old 12-03-2005, 11:52 AM   #3
raska
Member
 
Registered: Aug 2004
Location: Aguascalientes, AGS. Mexico.
Distribution: Slackware 13.0 kernel 2.6.29.6
Posts: 816

Rep: Reputation: 30
I prefer to install the first time from source, then if the package works fine and I like it as to keep it around for further installations, I'd do my own TGZ with makepkg.
 
Old 12-03-2005, 12:38 PM   #4
Okie
Member
 
Registered: Mar 2002
Location: Oklahoma
Posts: 966

Rep: Reputation: 34
if Pat V. does not make it as part of the distro i will compile from source, so my install of slacware is about half pat v. and half compiled source...
 
Old 12-03-2005, 01:55 PM   #5
Xian
Member
 
Registered: Feb 2004
Location: 33.31N -111.97W
Distribution: SuSE
Posts: 918

Rep: Reputation: 31
Quote:
Originally Posted by Okie
if Pat V. does not make it as part of the distro i will compile from source, so my install of slacware is about half pat v. and half compiled source...
How do you determine which pkgs to upgrade and when to do so?
In short, how do you keep track of this setup?
 
Old 12-03-2005, 03:19 PM   #6
mdarby
Member
 
Registered: Nov 2004
Location: Columbus, Ohio
Distribution: Slackware-Current / Debian
Posts: 795

Rep: Reputation: 30
I nearly always compile from source. It's much easier to find the source, and compiling gives you 100% control.
 
Old 12-03-2005, 03:38 PM   #7
Xian
Member
 
Registered: Feb 2004
Location: 33.31N -111.97W
Distribution: SuSE
Posts: 918

Rep: Reputation: 31
Quote:
Originally Posted by mdarby
I nearly always compile from source. It's much easier to find the source, and compiling gives you 100% control.
I like the idea, but I'm hesitant to do more without having a good example of how to keep track of the versions, dependencies, and what needs to be upgraded with which packages.

For example, let's say that I install foo_1 which depended upon foo_2 and foo_3, and these were all installed from source. Not so hard to remember unless, like Okie, there are a significant number of these on your system. How does one best track all of these and thereby keep the system properly maintained?
 
Old 12-03-2005, 03:44 PM   #8
mdarby
Member
 
Registered: Nov 2004
Location: Columbus, Ohio
Distribution: Slackware-Current / Debian
Posts: 795

Rep: Reputation: 30
Quote:
Originally Posted by Xian
How does one best track all of these and thereby keep the system properly maintained?
checkinstall
http://asic-linux.com.mx/~izto/checkinstall/

It's the first thing I install after the base install is complete.

As for dependencies, I see what ./configure tells me. If it needs something, I install it.
 
Old 12-03-2005, 04:28 PM   #9
MS3FGX
Guru
 
Registered: Jan 2004
Location: NJ, USA
Distribution: Slackware, Debian
Posts: 5,852

Rep: Reputation: 351Reputation: 351Reputation: 351Reputation: 351
I use checkinstall as well, helps with the upgrading at the very least.

But there is really no way to make sure everything is updated beyond keeping an eye on the websites for the software you have installed.

As for dependancies, you just note anything the software complains about while attempting to compile, and install that as well.
 
Old 12-03-2005, 04:29 PM   #10
Xian
Member
 
Registered: Feb 2004
Location: 33.31N -111.97W
Distribution: SuSE
Posts: 918

Rep: Reputation: 31
Quote:
Originally Posted by mdarby
checkinstall
http://asic-linux.com.mx/~izto/checkinstall/

It's the first thing I install after the base install is complete.
Sure, I've used that tool, and managing packages based on that method I certainly understand. I was just under the impression that the other posters I quoted were strictly installing from source, with no additional utilities that aided with managing the system packages. And if this were the case then I'd be interested in what method they do use for this function.
 
Old 12-03-2005, 04:57 PM   #11
Okie
Member
 
Registered: Mar 2002
Location: Oklahoma
Posts: 966

Rep: Reputation: 34
Quote:
Originally Posted by Xian
How do you determine which pkgs to upgrade and when to do so?
In short, how do you keep track of this setup?
when the author of the sourcode comes out with a new release i just delete the old installed package and compile the new one, a few times a week i just visit a few websites and take a quick peek at http://freshmeat.net/ once or twice a day,

the base system & Xorg is slackware - slapt-get updates that part,
 
Old 12-03-2005, 05:05 PM   #12
Xian
Member
 
Registered: Feb 2004
Location: 33.31N -111.97W
Distribution: SuSE
Posts: 918

Rep: Reputation: 31
Quote:
Originally Posted by Okie
when the author of the sourcode comes out with a new release i just delete the old installed package and compile the new one...
You then keep all the installed & compiled package folders on your system in case you want to go back and do a 'make uninstall'? And then afterwards remove and replace with the updated compilations?
 
Old 12-03-2005, 05:23 PM   #13
Okie
Member
 
Registered: Mar 2002
Location: Oklahoma
Posts: 966

Rep: Reputation: 34
Xian, make uninstall is something i never used, i usually just delete the executable from /usr/bin and check for any libs in /usr/lib and check for any directories in /usr/include & /usr/share

one other thing, this is just my personal home/office PC used just as a desktop/workstation and nothing running on it is absolutly crucial so if i mess it up i am only out a little time having to fix a few things or at worst having to reinstall the system, not like lives or business' are dependant on it...

i learned to be carefull about what i do so i do not spend all my time fixing things i broke, so if your carefull about what you do - you wont waste all your time fixing things that way you have more time to enjoy your PC productively...
 
Old 12-03-2005, 06:53 PM   #14
liquidtenmilion
Member
 
Registered: May 2004
Location: South Carolina
Distribution: Slackware 11.0
Posts: 606

Rep: Reputation: 31
I usually always use source, and then make a package for it. I currently have 100+mb of packages in ~/packages.

To do this all that is usually needed is.

1. Read documentation in tarball.
2. ./configure --help to find out all the additional options.
3. export CFLAGS="-O2 -march=i486 -mcpu=i686 -pipe";export CXXFLAGS="-O2 -march=i486 -mcpu=i686 -pipe" (editing them to whatever i need for that particular package.
4. ./configure --prefix=/usr --whatever-other-options
5. make
6 su
7 make DESTDIR=/work install
8. cd /work and then strip binaries, move/remove unnecessary/misplaced files, mkdir install, then add a slack-desc.
9. cd back into /work and do "makepkg programname-version-i686-1asw.tgz

Then i have a nice package that i can later remove/upgrade if needed. I can then do an rm -rf /work and i can remove the source code.
 
Old 12-04-2005, 05:38 AM   #15
Swift&Smart
Member
 
Registered: Jan 2003
Location: Hong Kong,China
Distribution: Slackware,OpenSUSE
Posts: 472

Original Poster
Rep: Reputation: 30
liquidtenmilion and all folks have given invaluable suggestions to me, thanks a lot.

liquidtenmilion,I personally prefer your option to make a slackware package because it's clear and intact if I want to remove/upgrade the package.However, can you point me to any website which you learned from regarding this package creation?

Okie, I have similar experience as you after compiled the source file if I want to delete them. But don't you think delete these files are difficult if you installed them from source files?Because it is not Windows,files are all kept in the Prgram Files by default. That's why I would like to ask the caption questions to see how you guys to deal with the package management. I do appreciate the advantages of using source files. However, I am more appreciative when I can manage my package systematically.

Thanks all you guys giving me many many good suggestions.

That's the new icon.
 
  


Reply

Tags
compile, package


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
Looking for a multiple file search and replace tool, prefer graphical haimeltjnfg Linux - Software 6 02-02-2005 11:53 PM
tgz file doesn't end in .tgz? detpenguin Slackware 4 05-15-2004 08:13 PM
Do you prefer Curses based or Graphical File Mangers? njbrain General 19 04-25-2004 11:27 PM
tgz vs. rpm vs. source? Joey.Dale Linux - Distributions 3 01-08-2004 10:02 PM
tgz files and source nny0000 Slackware 2 11-18-2003 05:18 AM


All times are GMT -5. The time now is 08:03 PM.

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
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration