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 03-21-2014, 01:16 AM   #1
J.D.
LQ Newbie
 
Registered: Jun 2013
Posts: 9

Rep: Reputation: Disabled
Building packages vs Binary


Is it better to build packages or simply slackbuilds binaries. (The convenient way)... I have trust issues. But as far as performance goes just wanted some opinions on this.
 
Old 03-21-2014, 01:21 AM   #2
dugan
Senior Member
 
Registered: Nov 2003
Location: Canada
Distribution: distro hopper
Posts: 4,625

Rep: Reputation: 1418Reputation: 1418Reputation: 1418Reputation: 1418Reputation: 1418Reputation: 1418Reputation: 1418Reputation: 1418Reputation: 1418Reputation: 1418
I don't understand the question.

My guess on what you're asking is this: if you want to build packages for Slackware and distribute them, is it better to to distribute the binaries or the SlackBuild scripts?

If that's what you're asking, my answer is this. You always distribute the SlackBuild scripts. Distributing the binaries in addition to the SlackBuild scripts would be appreciated, but it's not mandatory.
 
Old 03-21-2014, 01:23 AM   #3
J.D.
LQ Newbie
 
Registered: Jun 2013
Posts: 9

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by dugan View Post
I don't understand the question.

My guess on what you're asking is this: if you want to build packages for Slackware and distribute them, is it better to to distribute the binaries or the SlackBuild scripts?

If that's what you're asking, my answer is this. You always distribute the SlackBuild scripts. Distributing the binaries in addition to the SlackBuild scripts would be appreciated, but it's not mandatory.
My bad I meant "Build packages from source". Is it worth the hassle or is slackbuilds good enough?

Last edited by J.D.; 03-21-2014 at 01:24 AM.
 
Old 03-21-2014, 01:26 AM   #4
dugan
Senior Member
 
Registered: Nov 2003
Location: Canada
Distribution: distro hopper
Posts: 4,625

Rep: Reputation: 1418Reputation: 1418Reputation: 1418Reputation: 1418Reputation: 1418Reputation: 1418Reputation: 1418Reputation: 1418Reputation: 1418Reputation: 1418
The SlackBuild should be doing the exact same thing you'd be doing if you were building a package from a source tarball. If it's not, then you can edit the SlackBuild.

And if you have "trust issues", you can read the SlackBuild.

Last edited by dugan; 03-21-2014 at 01:27 AM.
 
1 members found this post helpful.
Old 03-21-2014, 01:35 AM   #5
J.D.
LQ Newbie
 
Registered: Jun 2013
Posts: 9

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by dugan View Post
The SlackBuild should be doing the exact same thing you'd be doing if you were building a package from a source tarball. If it's not, then you can edit the SlackBuild.

And if you have "trust issues", you can read the SlackBuild.
OK thanks I thought the slackbuilds were prebuilt binaries instead of source. So its just a script that builds it for you on your system is what you are saying.
 
Old 03-21-2014, 01:38 AM   #6
dugan
Senior Member
 
Registered: Nov 2003
Location: Canada
Distribution: distro hopper
Posts: 4,625

Rep: Reputation: 1418Reputation: 1418Reputation: 1418Reputation: 1418Reputation: 1418Reputation: 1418Reputation: 1418Reputation: 1418Reputation: 1418Reputation: 1418
Quote:
Originally Posted by J.D. View Post
OK thanks I thought the slackbuilds were prebuilt binaries instead of source. So its just a script that builds it for you on your system is what you are saying.
Yes.

There are probably other docs by now (I haven't been keeping up with SlackDocs), but here's a good primer:

http://slackbuilds.org/howto/
 
Old 03-21-2014, 01:57 AM   #7
ruario
Senior Member
 
Registered: Jan 2011
Location: Oslo, Norway
Distribution: Slackware
Posts: 1,817

Rep: Reputation: 817Reputation: 817Reputation: 817Reputation: 817Reputation: 817Reputation: 817Reputation: 817
@J.D. (a.k.a. Mercury305): 90%+ of all SlackBuilds do build from source and then package. However you will find a handful of SlackBuild scripts that just repackage a binary. The most common reason for SlackBuilds doing this is because the software is proprietary and the source code is unavailable (e.g. Chrome [unlike Chromium it includes some proprietary parts] and Opera). Other times people make SlackBuilds that repackage binaries because they are time consuming or require lots of resources to build (e.g. Firefox with PGO).
 
1 members found this post helpful.
Old 03-21-2014, 03:30 AM   #8
ruario
Senior Member
 
Registered: Jan 2011
Location: Oslo, Norway
Distribution: Slackware
Posts: 1,817

Rep: Reputation: 817Reputation: 817Reputation: 817Reputation: 817Reputation: 817Reputation: 817Reputation: 817
Quote:
Originally Posted by J.D. View Post
So its just a script that builds it for you on your system is what you are saying.
They are scripts that automate:
  • Unpacking the source (or precompiled binary)
  • Building the software (or reorganising it in the case of precompiled software)
  • Packaging the result into Slackware's native package format

SlackBuilds are often preferred to binary packages, particularly when you getting some of your software from unknown or not fully trusted sites of people. It gives you the convenience of being able to use native packing tools but allows you to review what is being done to make the package.

In the case of SlackBuilds.org most here would trust them to serve binaries but hosting a bunch of build scripts takes up less space, allows the user to tweak things and also learn something along the way.
 
Old 03-21-2014, 12:45 PM   #9
J.D.
LQ Newbie
 
Registered: Jun 2013
Posts: 9

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by ruario View Post
They are scripts that automate:
  • Unpacking the source (or precompiled binary)
  • Building the software (or reorganising it in the case of precompiled software)
  • Packaging the result into Slackware's native package format

SlackBuilds are often preferred to binary packages, particularly when you getting some of your software from unknown or not fully trusted sites of people. It gives you the convenience of being able to use native packing tools but allows you to review what is being done to make the package.

In the case of SlackBuilds.org most here would trust them to serve binaries but hosting a bunch of build scripts takes up less space, allows the user to tweak things and also learn something along the way.
OK that makes more sense.
 
  


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
[SOLVED] C++, building a binary, file inclusion... Netooo Programming 5 05-19-2012 02:11 PM
Building a slackbuild for a precompiled binary Cultist Slackware 1 11-20-2011 08:51 AM
Uninstalling non binary packages. stf92 Linux - Software 7 05-12-2009 04:52 PM
Building an only-one binary application demon_vox Programming 7 06-02-2006 09:11 PM
Building Binary LFS Tuvok Linux From Scratch 10 03-20-2005 07:09 PM


All times are GMT -5. The time now is 05:55 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