Slackware 13.1 (maybe with KDE 4.3.4)?

~sHyLoCk~ · 12-03-2009, 06:54 PM

Quote:

Originally Posted by dolphin77

There is no big issue about kde 4.3.4.

I just took the tree from slackware64-current/source/kde
put new source files to slackware64-current/source/kde/src
changed version in KDE.options to 4.3.4

and everything built as it should. I am running 4.3.4 for more than 1 day. And I donot really see any difference. Purhaps some bugs were fixed, but I do not see any difference as everyday user.

And there is no need to push for new release just because new kde bugfix was released. I believe, to get new release there should some major changes. For example new x server, which should be out next spring, I believe.

Anyway it is just my 0.005 cent.

Of course there is no change in appearance in KDE 4.3.4. It is a maintenance release. It's supposed to be a bunch of bugfixes here and there. Check out the changes http://www.kde.org/announcements/cha...3_3to4_3_4.php

BrZ · 12-05-2009, 08:47 AM

Quote:

Originally Posted by dolphin77

I just took the tree from slackware64-current/source/kde put new source files to slackware64-current/source/kde/src changed version in KDE.options to 4.3.4 and everything built as it should.

@dolphin77

Heeeeeelp... I'm stucked building kdebindings-4.3.4. It's failing with ruby 1.9.1. Any clues if I just downgrade to ruby 1.8.7 the 'thing' will compile?

TIA

edit: Downgraded to ruby 1.8.7 and failed again =[

dolphin77 · 12-05-2009, 09:02 AM

Quote:

Originally Posted by BrZ

@dolphin77

Heeeeeelp... I'm stucked building kdebindings-4.3.4. It's failing with ruby 1.9.1. Any clues if I just downgrade to ruby 1.8.7 the 'thing' will compile?

TIA

edit: Downgraded to ruby 1.8.7 and failed again =[

In fact I have no idea. I have 64-current with multilib32 from alien here. Maybe I have some additional packages here from slackbuilds.org. But for me it ran without any errors in any kde package.

cheers.

BrZ · 12-05-2009, 09:07 AM

Mine is current64-pure... maybe this can be related. Thanks for the quick reply.

dolphin77 · 12-05-2009, 09:24 AM

Quote:

Originally Posted by BrZ

Mine is current64-pure... maybe this can be related. Thanks for the quick reply.

Hm, I checked. I build kde-4.3.4 before recent ruby update in current and it worked then. But I checked right now (after ruby update) and it fails to build kdebindings. You are right.

Rupa · 12-05-2009, 10:49 AM

Quote:

Originally Posted by dolphin77

Hm, I checked. I build kde-4.3.4 before recent ruby update in current and it worked then. But I checked right now (after ruby update) and it fails to build kdebindings. You are right.

There was another ruby update today in current and it helps. kdebindings do compile again.

BrZ · 12-05-2009, 03:50 PM

@Rupa

Thanks, I'll try again. Fist time it failed when kdepim (or pimlibs) asked for Akonadi. Installed the package and started the individual build when it failed to compile the bindings. Even with downgraded Ruby (1.8.7) the build failed. If it fails again, no problem.

edit: The thing was built, but only after editing 'kdebindings.SlackBuild' and disabling krossruby as it keep failing:

Quote:

-DRUBY_EXECUTABLE=/usr/bin/ruby \
-DRUBY_INCLUDE_PATH=/usr/include/ruby-1.9.1/ruby \
-DRUBY_LIBRARY=/usr/lib64/libruby.so.1.9.1 \
-DENABLE_KROSSRUBY:BOOL=OFF \

salemboot · 02-04-2010, 11:16 PM

spell checker fixed in Koffice yet?

gargamel · 02-05-2010, 03:50 PM

Quote:

Originally Posted by onebuck

[...]

It's that loads of people in the GNU/Linux community look down at Slack as it's still not GUI based install. [...]

I agree with you. I couldn't care less, however, if the installer has a GUI or is curses or text based. As long as it reliable guides me through the setup process, it's ok for me. I admit, that GUI installers, such as the one of SuSE, have some appeal, but I wouldn't like it if it didn't work. As a matter of fact, the SuSE installer and the Slackware installer both work great for me. Different approache can deliver equally good results.

gargamel

AGer · 02-05-2010, 04:33 PM

Quote:

Originally Posted by ~sHyLoCk~

lol.

Back on topic, KDE4.3.4 should be in 13.1 but 4.4 will require rebuilding apps with qt4.6, and since this is a version jump, a lot of new features will be introduced, testing could take a while.

Those interested in Qt will find 13.1 with KDE 4.3 0-day outdated. If 4.4 is released Fabruary then 13.1 can be released April or May with 4.4.1. Everything will match - current Qt, bugfix release of KDE, and normal period between releases.

salemboot · 02-06-2010, 12:09 AM

I hope we get a good word processor on the disc this time.

The KOffice team is happy to release KOffice 2.1.1, the first bugfix release in the 2.1 series. This release contains no new features but a number of bugfixes for most of the components in KOffice 2.1. More details of the 2.1.1 release can be found in the changelog. This version of KOffice is translated to no less than 27 languages.

As was noted in the announcement for 2.1.0, KOffice 2.1.1 is probably still not usable for production work.

cwizardone · 02-06-2010, 07:56 AM

Quote:

Originally Posted by salemboot

I hope we get a good word processor on the disc this time..... As was noted in the announcement for 2.1.0, KOffice 2.1.1 is probably still not usable for production work.

And a complete waste of disk space.

cwizardone · 02-06-2010, 07:59 AM

Quote:

Originally Posted by onebuck

The way that Slackware is contained. Right now we have order copies that are dual sided. We have download mirrors for a particular arch. Slackware doesn't have a LiveCD unless you consider the Install CD/DVD as one. Sure there's 'Slax' but with today's technology we have media choices that could be used for a Live distribution. So to be productive and available a repackage would be nice...

Agreed. Thanks for taking the time to reply.

boler · 02-25-2010, 04:10 AM

When will Slackware 13.1 be released?

OR

What is the criteria to judge when Slackware 13.1 "is ready"?

ponce · 02-25-2010, 05:02 AM

no dates or next version number (could be 14 also) are known.
the criteria has always been: "is ready when it's ready".