LinuxQuestions.org
View the Most Wanted LQ Wiki articles.
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 03-14-2007, 09:26 AM   #16
gnashley
Amigo developer
 
Registered: Dec 2003
Location: Germany
Distribution: Slackware
Posts: 4,749

Rep: Reputation: 461Reputation: 461Reputation: 461Reputation: 461Reputation: 461

I've written a tool which makes compiling and packaging a real breeze most of the time.

http://distro.ibiblio.org/pub/linux/...1.0-i486-1.tgz

Login as root, install the above package.
Then just type `src2pkg tarballname`. Can't get much easier than that. If it turns out that you need to pass extra options to configure you can do that and much more by using the src2pkg options.
 
Old 03-14-2007, 11:21 AM   #17
GrapefruiTgirl
Guru
 
Registered: Dec 2006
Location: underground
Distribution: Slackware64
Posts: 7,594

Rep: Reputation: 550Reputation: 550Reputation: 550Reputation: 550Reputation: 550Reputation: 550
Thanks for that, Gnashley I will be checkng into it shortly. Already downloaded it, and it looks very handy; nice work!
 
Old 03-14-2007, 04:53 PM   #18
bioe007
Member
 
Registered: Apr 2006
Location: lynnwood, wa - usa
Distribution: archlinux
Posts: 654

Rep: Reputation: 30
Quote:
Originally Posted by mattydee
Are you being sarcastic? I can't tell... anyways, yes you are correct. Most programs will have to be installed as root.
well, I wasn't but if it gets a laugh out of anyone - then i was

the clarification by onebuck is really what I was looking to elicit. + sometimes when I am trying to compile on my own and working in different terminal windows I'll accidentally ./configure as root, which forces me to make as root, etc

if it wasn't necessary to 'su' to make install then I'd be aggravating myself for no reason.

I too liberally apply checkinstall.

? how do you tell if its a user package? also does it still go to /var/log/packages? can someone point me to the 'M' in rtfm about this?

(and no, that wasn't sarcasm ;D )

@gnashley- yes thanks for the tool. I am d/ling it now.

another ? should I feel kind of lame for relying on all these package tools to install stuff? I use whatever I can find at linuxpackages, slackbuilds and the CD extras of course. But should I endeavor to learn the intricacies of this stuff myself? Whats the benefit (besides satisfying my abnormal geek curiosity)?

Last edited by bioe007; 03-14-2007 at 04:57 PM.
 
Old 03-14-2007, 05:06 PM   #19
adriv
Member
 
Registered: Nov 2005
Location: Diessen, The Netherlands
Distribution: Slackware 14.1
Posts: 659

Rep: Reputation: 38
Even more simple:
Rightclick the tar.* --> Extract --> click on the new folder --> press F4 --> ./configure --> make --> (as root) checkinstall --> installpkg.
Of course always read the README and/or INSTALL in advance.

src2pkg is also a fine tool (maybe even more handy).
Lets you install .deb and .rpm files as well!

Last edited by adriv; 03-14-2007 at 05:08 PM.
 
Old 03-15-2007, 03:03 AM   #20
gnashley
Amigo developer
 
Registered: Dec 2003
Location: Germany
Distribution: Slackware
Posts: 4,749

Rep: Reputation: 461Reputation: 461Reputation: 461Reputation: 461Reputation: 461
"how do you tell if its a user package?" Do you mean if it should be installed to /usr? If so, i think that nearly anything you package for use with installpkg should be installed to /usr (except for stuff like KDE or anything that *needs* to be installed to another prefix. If you are compiling and installing with 'make install', then the program shouild go to prefix /usr/local.

Learning the ins and outs of compiling is fun and can also be quite challenging. I've spent the last two years working on src2pkg and teaching it what I learn. It can now compile, on it's own, many programs that I couldn't compile even manually two years ago. Having a look through the src2pkg the configure_source function may provide some tips for configuring difficult sources. For instance, a few months ago I discovered the 'nearly magic' command 'autoreconf -if' which will update all the config files and stop *lots* of errors. src2pkg uses autoreconf when it finds autoconf sources without an executable configure script -like CVS sources.

Most sources can be configured and compiled as user and then installed as root, but there are programs which must be compiled as root in order to work correctly -there are others which must be compiled as user, but this is less common. When this is the case, you can still use the src2pkg tools by untarring and compiling as user, then su to root and make the package using trackinstall instead of src2pkg.
src2pkg and trackinstall can also write the script for you, if you need or want to keep a record the build for repeatability.
 
  


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
Apache newbie question.. (very newbie question) tarballed Linux - Newbie 1 02-07-2003 08:41 PM
RE: Suse 8.0 hardware question {newbie question, pls help} Radiouk Linux - Distributions 2 06-04-2002 12:53 PM
RE: Samba question pls help {Newbie question} Radiouk Linux - Networking 4 06-03-2002 06:40 PM
Security question {newbie question} Radio Linux - Security 3 05-17-2002 06:32 PM


All times are GMT -5. The time now is 07:44 PM.

Main Menu
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