KDE 4.2.1 for Bluewhite64 12.2 has landed!

arny · 03-04-2009, 01:25 AM

Yucatan "Kenjiro" Costa, has posted the following in the Bluewhite64 Linux forums:

Quote:

OK, here I go again. I am creating this thread so we can talk about KDE-4.2.x (yes, all versions inside the 4.2.something "line").

Yesterday I compiled and packaged KDE-4.2.1. Now I am testing it and as soon as possible I will upload it to the repository, of course i will let you know.

Let's see how well it runs

KDE 4.2.1 Packages can be found here: http://data.linux64packages.net:8080...2.2/kde-4.2.1/

Enjoy!

piratesmack · 03-05-2009, 08:57 AM

Awesome

But where can I find the SlackBuilds?

arny · 03-05-2009, 09:03 AM

From the README:
"# All these packages were created by me, Yucatan "Kenjiro" Costa,
# based on the SlackBuild scripts of Robby Workman."

Slackbuild are also here:
http://data.bluewhite64.com/bluewhit...g/source/kde4/

Alien Bob · 03-10-2009, 04:11 PM

Quote:

Originally Posted by arny

From the README:
"# All these packages were created by me, Yucatan "Kenjiro" Costa,
# based on the SlackBuild scripts of Robby Workman."

Slackbuild are also here:
http://data.bluewhite64.com/bluewhit...g/source/kde4/

That is not true of course - only the sources for the older KDE 4.2.0 packages can be found there.
Like with all the other packages at http://data.linux64packages.net:8080/ you will not find the program sources, and the SlackBuilds & patches used to create these packages are also missing.

Why?

Eric

kenjiro · 03-11-2009, 02:14 PM

Hello there alienBOB. The SlackBuilds missing are my fault.

I didn't take the time (because I still haven't got it) to re-edit my slackbuilds and then upload them to the repository. The thing is the slackbuilds I use point the $TMP variable to /files/linux/tmp (my particular setup), plus they automaticaly install all the KDE (and deps) packages as soon as they are created. Since I don't think everyone would have that directory (/files/linux/tmp) and perhaps they wouldn't want the scripts to install everything right after package creation, I have to create the "normal" copies of such scripts, that is, ones that use "/tmp" for temporary directory and which doesn't install everything.

For the KDE-4.2.1 source code, everything can be downloaded from KDE site.

I remember arny saying (don't remember the exact post of forum) that he just can't host all the sources on BW64 repository, because he doesn't have that much disk space available. So that's why I didn't upload the sources along with my packages.

If you have more questions, please let me know

May the Force be with you!

Kenjiro

Alien Bob · 03-11-2009, 02:26 PM

There is of course a controversy about the obligation to host the source tarballs of any binary packages you offer for download on a website - Arny and I have different viewpoints on this.

But regardless of that, it is always a good thing to make the SlackBuilds and patches available that were used to create those packages. Not just to see how the packages were built (I will never trust 3rd party package repositories that do not offer the complete build script/instructions along with the binaries), but there are always people who want to rebuild a package because they want to link it against software not normally present on {Slackware,slamd64,Bluewhite64} to enable additional features. Think of pulseaudio, lame, faac, all kinds of external apps.

Eric

arny · 03-12-2009, 07:39 AM

It looks like some packages started to include in the package the build scripts, like libgcrypt.SlackBuild, libgpg-error.SlackBuild from the --current tree

Code:

mkdir -p $PKG/usr/doc/$PRGNAM-$VERSION
cp -a \
  AUTHORS BUGS COPYING* ChangeLog INSTALL NEWS README README.SVN THANKS TODO VERSION \
  $PKG/usr/doc/$PRGNAM-$VERSION
cat $CWD/$PRGNAM.SlackBuild > $PKG/usr/doc/$PRGNAM-$VERSION/$PRGNAM.SlackBuild

Alien Bob · 03-12-2009, 07:59 AM

Quote:

Originally Posted by arny

It looks like some packages started to include in the package the build scripts, like libgcrypt.SlackBuild, libgpg-error.SlackBuild from the --current tree

[/CODE]

Yes, but that is only because these particular SlackBuild scripts have their origin in either http://slackbuilds.org, my own or Robby Workman's repository. Slackware will not include SlackBuild scripts in the document directory by default.

In fact we are actually removing those SlackBuild copy commands from the scripts we edit nowadays, if we find them.

Eric