LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (http://www.linuxquestions.org/questions/slackware-14/)
-   -   Differences between packages of AlienBoB Repository and Slackbuilds (http://www.linuxquestions.org/questions/slackware-14/differences-between-packages-of-alienbob-repository-and-slackbuilds-939807/)

JohnV2 04-14-2012 01:26 PM

Differences between packages of AlienBoB Repository and Slackbuilds
 
Hi,

Like the question says, in general terms, whats is the different between packages of AlienBoB Repository and Slackbuilds?

I know some alien-pkg builds from source, but others I don't know and don't see any readme about my doubt.

Cheers,
John

BCarey 04-14-2012 01:52 PM

AlienBob's repository contains both Slackbuild scripts and installable packages made by Eric Hameleers, who is on the Slackware team. The packages are compiled on clean systems and are very high quality. You could also use his Slackbuilds to compile the packages on your own machine.

Slackbuilds.org is a collaborative site which has high-quality build scripts but NO packages. There are various maintainers of the different build scripts on the site and there is a wonderful tool called sbopkg which allows you to queue up packages and dependencies and then downloads the sources and builds and installs them for you.

Brian

kingbeowulf 04-14-2012 04:50 PM

AlienBOB's slackbuilds also differ a bit in certain philosophical aspects from Slackbuilds.org - examples include libreoffice and vlc. He will also provide updates to some core Slackware packages (ie KDE) for the adventurous. SBo provides quality scripts that stay within the core system dependencies (ie kernel, QT, GTK etc.). Updating core packages can be a real nightmare if you do not now what you are doing.

I use his calibre slackbuild as he tracks a newer version than SBo and gets all the crazy dependencies to work out for Slackware-stable.

JohnV2 04-14-2012 05:12 PM

Hey thanks Brian, but I know what you saying, yeah beawulf I use calibre too for the dependence thing haha... but I mean in more technical matter, what is the differences?. Like kvm, calibre, blender, clamav, vlc or some other apps.

And the answers brings me a old doubt I have from time to time, why Eric don't sends his script's to slackbuilds?

regards,
John

BCarey 04-14-2012 06:07 PM

Slackbuilds are simple scripts and AlienBob's are generally very well documented. So if you want a "more technical" answer then you should look at the scripts themselves and see what they are doing. AlienBob's scripts will often "build in" the dependencies where slackbuils.org scripts will require that the dependencies be built separately.

Brian

kingbeowulf 04-15-2012 01:51 AM

Also, many of the added dependencies in AlienBOB's scripts are too invasive or not compatible with mainline Slackware-stable. Hence, he "builds in" some of them, and some others are just for convenience (e.g. script grabs and compiles everything automatically in the right sequence). SBo just includes those dependencies that don't interfere with Slackware-stable.

Alien Bob 04-15-2012 04:51 AM

Quote:

Originally Posted by kingbeowulf (Post 4653050)
Also, many of the added dependencies in AlienBOB's scripts are too invasive or not compatible with mainline Slackware-stable. Hence, he "builds in" some of them, and some others are just for convenience (e.g. script grabs and compiles everything automatically in the right sequence). SBo just includes those dependencies that don't interfere with Slackware-stable.

I don't know where you are getting that idea from.
All my packages (compiled using the SlackBuild scripts I also provide) in my repository at http://connie.slackware.com/~alien/slackbuilds/ are 100% compatible with Slackware. I provide packages for multiple stable versions and do not build them for slackware-current generally. The packages in this repository are add-ons to Slackware, i.e. the packages do not conflict or replace anything in Slackware (with some exceptions like MPlayer for which I also wrote the official Slackware script).

I have other repositories, like "ktown" at http://alien.slackbook.org/ktown/ where I provide more up to date versions of KDE than you can find in Slackware. The ktown repository will replace a lot of official Slackware packages... naturally.

There is also my multilib repository at http://connie.slackware.com/~alien/multilib/ where I provide replacements for Slackware's own gcc and glibc and provide add-on packages which make it possible to run and compile 32-bit software on 64-bit Slackware.

Those are three separate repositories, with three different goals.
I always provide SlackBuild scripts, patches and sources so that you can try and build the packages yourselves, but the main purpose is to provide packages. The http://slackbuilds.org/ site has a goal which is opposite of this: that site provides only the SlackBuild scripts and expects you to build the packages (and with the use of sbpokg and its queue file system, that is not complicated to do).

I will not submit my SlackBuild scripts at http://slackbuilds.org/ because as others stated already, my scripts are coneptually different, and do things we do not want from a script at SlackBuilds.org (like downloading missing source tarballs automatically, or building static packages which use a lot of different sources - like VLC). I am an admin at http://slackbuilds.org/ but I keep these businesses strictly separated.

Eric

kingbeowulf 04-19-2012 09:53 PM

Alien Bob,

Perhaps my statement was insufficiently precise. I greatly appreciate your effort in creating those packages. However, your answer proves my point. Although ktown will eventually make it into stable, it is not currently and getting it to all compile for Slackware-13.37 would be a pain in the ass for most of us. The multilib repository, which I also greatly appreciate, is another example. It is very useful for many, not officially supported by PV, and extremely invasive to Slackware-13.37, and would be a right pain in the ass for me to try to do on my own. Heck, thats why I jumped onto fred's SLAMD64!

Your "extra" repository is also very useful. I fought unsuccessfully with calibre until I found your blog entry - saved my sanity!

I stand by my opinion: SBo is for programs any yutz like me can get compiled on STOCK Slackware. Your repository is for the tough stuff that won't easily compile on STOCK Slackware without a lot of work, along with a handy shortcut to binary packages that just plain work.

Thanks,
Ed


All times are GMT -5. The time now is 01:06 PM.