LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (http://www.linuxquestions.org/questions/slackware-14/)
-   -   Can I bring KDevelop only to current? (http://www.linuxquestions.org/questions/slackware-14/can-i-bring-kdevelop-only-to-current-4175477359/)

Z038 09-16-2013 04:50 PM

Can I bring KDevelop only to current?
 
I'm running 14.0-64 plus security update packages. Normally I prefer to avoid the bleeding edge and just do full version upgrades rather than try to keep -current. But I'd like to bring KDevelop up to the -current level.

These are the packages from -current that I think I need:

kdevelop-4.5.1-i486-1.txz
kdevelop-pg-qt-1.0.0-i486-1.txz
kdevelop-php-1.5.1-i486-1.txz
kdevelop-php-docs-1.5.1-i486-1.txz
kdevplatform-1.5.1-i486-1.txz

I might need a couple of others, like kdelibs and kdesdk.

Am I likely to run into problems if I upgrade these packages without the rest of KDE?

Is it ok to upgrade selectively using packages from -current, or would I be better off building from source, or upgrading all the KDE packages, or upgrading everything (i.e., fully -current)?

I think building from source could be a bit of work, as there are some dependencies that I don't see in the default 14.0 packages, like Qt-devel.

Didier Spaier 09-16-2013 04:59 PM

I don't use KDE so I didn't try, but I suggest you install packages for KDE-4.10.5 provided by Alien BOB here

Z038 09-16-2013 06:06 PM

Thank you Didier. That will certainly make it easy for me!

Thanks also to Alien Bob for all your tremendous support for the rest of us slackers.

Z038 09-18-2013 04:06 PM

The upgrade to KDE 4.10.5 using Alien Bob's packages went perfectly.

Later, I ran slackpkg update and slackpkg upgrade-all to pick up recently rebuilt packages with security updates (i.e., the glibc, firefox, and thunderbird packages that were announced on the slackware-security list earlier today). slackpkg wanted to "upgrade" all of the packages that were included in Alien Bob's 4.10.5 set back to the 4.8 level.

I blacklisted those packages in the slackpkg blacklist by adding an entry at the bottom:

Code:

# You can blacklist using regular expressions.
#
# Don't use *full* regex here, because all of the following
# will be checked for the regex: series, name, version, arch,
# build and fullname.
#
# This one will blacklist all SBo packages:
#[0-9]+_SBo
[0-9]alien

It did the trick, but I'm not sure what the warning about not using *full* regex means. Is the way I added it correct and the recommended way of dealing with this?


All times are GMT -5. The time now is 09:07 AM.