Prepackaged Binary vs. Locally Compiled Source

Q&A, advice, reviews, and news about the computers, phones, TVs, stereos, and pretty much anything else that can't be easily whittled out of a stick or chipped out of stone.
Locked
RyuuNoSenshi
Redshirt
Posts: 56
Joined: Fri Jul 04, 2003 2:37 am
Location: Somewhere in subspace
Contact:

Prepackaged Binary vs. Locally Compiled Source

Post by RyuuNoSenshi » Sat Jul 12, 2003 8:32 pm

Since my switch to Linux I've become an even greater advocate for Open Source. The reason being is that I've had less trouble with compiling and installing from source than I've had with binaries(in either windows or linux). If something goes wrong with my compile I'm free to track down the source of the problem and fix it. With prepackaged binaries it's a lot harder to fix(windows binary packages especially). I can't even begin to count the number of times a window's binary package would screw up(in the middle of an install even!) and I'd be left looking for a solution(sometimes none could be found). Compiling from source also allows for the program to run faster because the compiled optimizes the code to run on the current hardware.

Binaries have some saving graces. One being the simpleness of the install(for people without the knowledge on how to troubleshoot complex problems). Binaries also don't need header files(such as the kernel source) in order to be installed.

But I personally prefer to know EXACTLY what's being installed on my system. With binary packages you only have the developer's word that he didn't give you a virus or a program that will erase your hard drive. With source code on the other hand such a thing would be impossible to hide. Source code also gives you the chance to make improvements in your software. Open Source in particular gives you the safty of the GNU license(which is what most Open Source is released under). As well as the freedom to base new programs off of the current code.

Though binaries are simple to install, it doesn't seem worth it in the end. Open Source allows the program the bloom and mature quickly through contribution from the community. Closed source binary packages don't grow nearly as quickly and get only bug reports from the community(it's up to the developers to fix those bugs). I'll always take source over binary. Ohh and source code is easy to port from platform to platform, but binaries can't be.
Me: Alright I'll stand here...try to crush me with the...*the Warthog lands on top of me*
Matt: Done and done.
Me: Ahh! My Corpse is stuck in the tire!

Bruce
Redshirt
Posts: 295
Joined: Tue Feb 18, 2003 12:41 pm
Location: Melbourne
Contact:

Post by Bruce » Sun Jul 13, 2003 4:13 am

Binaries are good as long as they are regulated. Being a debian user I use binaries all the time if they come from the official debian mirror, because to be there they must have all of their dependancies, must conform to debian standard, must have an open source license, and mustnt break anything.

If I am downloading from other sources then I would probably choose source, unless it was something with a large number of dependancies.
Just because life sucks, it doesnt mean you have to care.

cpo
Redshirt
Posts: 3
Joined: Sun Jul 13, 2003 4:21 pm
Location: Dresden / Germany
Contact:

Re: Prepackaged Binary vs. Locally Compiled Source

Post by cpo » Sun Jul 13, 2003 5:31 pm

Imho is the BSD port system a good way in the middle between these two alternatives.

You have a huge tree with informations about the "ports" (that would be your precompiled packages if they where precompiled *g*)

But in each directory you can build the port by yourself.

If the build was successfull you can install a port and it is registrered in the package database, so that you can uninstall it easily.

The whole is dependency-aware so you don't break your system by installing a port.
And it's ultra-easy if you use portinstall (it's in the ports *g*)

An example:

you want to intall xchat *g*

cd /usr/ports/xchat && make install distclean

or portinstall xchat

There is also a linux-distribution that uses a similar mechanism, but i don't remember the name ^^''''
I can look it up if somebody is interested (:

cpo
$_="-|";open(_)||print"creaJklrnue osrhptt,aeh ";while(<_>){$}=5;s/(.{$}})(.)/(print$2),$1/eg while--$};print;}

Webphisher
Redshirt
Posts: 7
Joined: Wed Jul 16, 2003 7:25 am
Location: Colorado
Contact:

Post by Webphisher » Wed Jul 16, 2003 8:30 am

The only time I dont like compiling the source code myself, is in the case like when I was first learning linux, and i got tossed in and told learn to swim. I tried building QT, and it took me hours of fixing the problems with the build code. Only saving grace I had was basic coding skills back then.

But I myself still would rather build and install on my own terms. More fun than binaries :D
Looking for an anime review, or want to make one, check out neurobox.gotdns.org

User avatar
elturcin
Redshirt
Posts: 306
Joined: Fri Feb 14, 2003 10:41 am

Post by elturcin » Wed Jul 16, 2003 10:21 am

cpo, Gentoo linux.
--
!

User avatar
Martin Blank
Knower of Things
Knower of Things
Posts: 12709
Joined: Fri Feb 07, 2003 4:11 am
Real Name: Jarrod Frates
Gender: Male
Location: Dallas, TX
Contact:

Post by Martin Blank » Wed Jul 16, 2003 5:16 pm

There are reasons to avoid compiling yourself, depending on what you're doing. If you're using something like OpenBSD, or installing security software, it may well be a better idea to use the binaries because they have been through a more thorough security vetting process than you're likely to be able to go through on your own. They will have been built on systems that may be more demonstrably secure than your own, and using compilers with appropriate options to mimimize the chances of things like buffer overflows getting in.
If I show up at your door, chances are you did something to bring me there.

Locked

Who is online

Users browsing this forum: No registered users and 1 guest