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 05-27-2008, 08:56 PM   #1
chexmix
Member
 
Registered: Apr 2002
Location: Arlington, MA
Distribution: Slackware, Debian, OpenBSD
Posts: 210
Blog Entries: 15

Rep: Reputation: 17
question(s) concerning SlackBuild scripts


Hi all -

I recently started looking into creating a couple of SlackBuild scripts for my own use and (should they work!) submission to slackbuilds.com. Seems not only fun but right instructive-like.

Now, my understanding of the section on "Setting Up Your Build Environment" part of the tutorial re: how to do this on SlackWiki is that the build environment _must_ include the source code for the relevant release of Slack _in its entirety_ ... is that correct? I just want to (cough) make sure because, my machine being the multi-boot thing it is, I might need to shuffle to make more space for all this, and it might even involve evicting the distribution next door.

So I'm triple-checking, is all.

Thanks,

Glenn

PS: I guess I should ask whether anyone can tell me how much space we're talking about ...
 
Old 05-27-2008, 09:12 PM   #2
TSquaredF
Member
 
Registered: Dec 2005
Location: "The South Coast of Texas"
Distribution: Slackware64-current
Posts: 490
Blog Entries: 1

Rep: Reputation: 55
Quote:
the build environment _must_ include the source code for the relevant release of Slack _in its entirety_ ... is that correct?
I don't think that it means the Slackware sources, but the package sources (of the packages you have built/are building). I have a complete 12.1 mirror on a spare partition (the sources sometimes come in handy), but I've never had to use them for building a package. My system entails a directory named "packages", then under it individual directories for each package. The individual directories contain the final package and a directory named "build" that contains all the build scripts & the source tar.gz for the program.
Regards,
Bill
 
Old 05-27-2008, 09:25 PM   #3
chexmix
Member
 
Registered: Apr 2002
Location: Arlington, MA
Distribution: Slackware, Debian, OpenBSD
Posts: 210
Blog Entries: 15

Original Poster
Rep: Reputation: 17
Thanks Bill.

Just to clarify, here is what I am seeing at

http://www.slackwiki.org/Build_Environment:

jjdm writes:

"/home/slackware/source In this directory I've placed the whole slackware-source because maybe I have to temporarily build another package to build a new one because of header files and stuff."

and robw810 writes:

"The /shared/os_files/slackware/slackware-(version)/source/ directory contains all of the source files (it's copied directly from the cdroms) from that release of Slackware."

... so that's where my impression and/or confusion comes from ...

gb
 
Old 05-27-2008, 09:49 PM   #4
T3slider
Senior Member
 
Registered: Jul 2007
Distribution: Slackware64-14.1
Posts: 2,260

Rep: Reputation: 645Reputation: 645Reputation: 645Reputation: 645Reputation: 645Reputation: 645
Unless you're doing something pretty complex, you shouldn't need the sources (and if you do need the source for an app, you could probably just download the source for that specific app). This is only really required if the app is a dependency and the app you're compiling needs the header files from the dependency, which may not be present on your system. For most tasks, however, you will not need the sources. I have written and used many SlackBuilds and I've never had to use sources for another package. Even if an app has many dependencies, usually it doesn't require the compiled sources of the other app -- it'll usually just search for files on your system during the ./configure command and it'll be happy with that.

Bottom line: at this point, don't even worry about it. If you ever come across an app that errors out (or doesn't work) upon compilation, and you have reason to suspect that it may be failing because it needs the headers from a dependency, then by all means download the dependency's sources and compile them (and inform the new app about the location of the dependency's sources). However, you will probably never need this -- or, if you do, it'll be exceedingly rare.
 
Old 05-28-2008, 05:32 AM   #5
chexmix
Member
 
Registered: Apr 2002
Location: Arlington, MA
Distribution: Slackware, Debian, OpenBSD
Posts: 210
Blog Entries: 15

Original Poster
Rep: Reputation: 17
Many thanks to you both for the replies.

I will try a SlackBuild or two and see how it goes.

gb
 
  


Reply

Tags
slackbuild


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
SlackBuild scripts stu_mueller Slackware 15 04-04-2008 01:03 AM
slackbuild question stormtracknole Slackware 2 11-13-2006 02:24 PM
Rebuilding a Slackware Package With Slackbuild Scripts Woodsman Slackware 11 10-14-2006 05:08 AM
Using slackbuild scripts Steve50 Slackware 3 10-11-2006 02:42 AM
Project FFMpeg (SlackBuild scripts) shilo Slackware 3 10-05-2005 10:17 AM


All times are GMT -5. The time now is 10:29 AM.

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