The what should be updated in -current thread

Before i forget it, there is also a new version for libjpeg [1], v8d1 (for "Series 8d"). -current has v8a.

Will this be updated or it could cause problems with other packages that depend on it?.

[1] http://jpegclub.org/support/

Originally Posted by hba Before i forget it, there is also a new version for libjpeg [1], v8d1 (for "Series 8d"). -current has v8a.

Or better be replaced by libjpeg-turbo
http://slackbuilds.org/repository/14...libjpeg-turbo/

Originally Posted by franzen Or better be replaced by libjpeg-turbo http://slackbuilds.org/repository/14...libjpeg-turbo/

i found a thing that won't compile with it

Originally Posted by genss i found a thing that won't compile with it

Oh? What was that?

I didn't know about libjpeg-turbo but in any case, Debian already is using it: https://wiki.debian.org/LJTTransition

Originally Posted by Alien Bob Oh? What was that?

something missing in a header, can't remember
was a while ago and there was a bug report

gnutls 3.4

Originally Posted by hba I didn't know about libjpeg-turbo but in any case, Debian already is using it: https://wiki.debian.org/LJTTransition

thanks Antonio for the link: those transition pages in the debian wiki (I spotted also the wxwidgets one) are very useful as a reference.

What's the difference between wxwidgets, wxpython, and wxgtk other than the last two having specific toolkit bindings, and wxpython has wxgtk already incorporated?

Originally Posted by BeaStiE35 Whole distro !

I mean it !!!

Originally Posted by BeaStiE35 I mean it !!!

Thank you for such a wonderfully helpful suggestion and followup comment.

Originally Posted by rworkman Thank you for such a wonderfully helpful suggestion and followup comment.

Robby you almost made me spill my drink. Hahahahaha. Perfect.

emacs 24.5

Originally Posted by rworkman Thank you for such a wonderfully helpful suggestion and followup comment.

But he meant it!

Speaking of updates, I've been wondering if we should begin looking into adding Wayland and any needed support libraries for it like libinput, libxkbcommon, as well as have projects rebuilt and linked to Wayland, officially integrated into Slackware.

I know this is an odd mentioning, but because some projects are now utilizing Wayland based rendering protocols, maybe it could be looked into, as well as enabling support in projects like KDE and such to use Wayland protocols, and maybe even see about using a heavily Slackwareified Weston in some way, though I think this may require a few extra packages, or at least a minimal shared object library if necessary for anything missing.