The what should be updated in -current thread

If it gets some testing soon, there's a good chance of that happening. My advice, get some Slackbuilds made.

I bought SSD recently.Crucial M500.

So I think smartmoontools worth be upgraded. Some attributes are missing in current package.

I think cryptosetup package in current is too old. Default cipher mode has changed to more safe.

My advice, get some Slackbuilds made.

by me?

I do think it's worth pointing out that if MPlayer were to be replaced with MPV, then mencoder would be replaced with ffmpeg (which mpv has as a dependency).

MPlayer just treats ffmpeg as part of its own source code (that's why Alien Bob's MPlayer SlackBuild downloads ffmpeg).

@everyone chewing out ivandi

He is able to make suggestions just like anyone else. I would think it could be done without the insults, but he still has a valid use for making that suggestion (and as Alien Bob also said, it doesn't introduce automatic dependency resolution to the OS. It just makes it easier for those who don't want to install a FULL install, just to run a webserver.

I would think we could be a little more professional here. There's a lot of tools that fit into a similar bubble as ivandi's, so I don't see why him asking for a simple tool to be included is such a problem. He threw it out there, it's not our job to make the decision. The Slackware dev team can consider it or ignore it. These pissing matches are getting old.

Originally Posted by ReaperX7 Ah, thanks for clearing that up Dugan. Well, in any case MPlayer is possibly a wider hitting package though the limits of it are noted, but however, keeping the traditional MPlayer package will probably take precedent. I see a few reasons to upgrade to another (maybe better) media player, but not enough to replace two parts of the whole and relegate them out to other packages (namely gmplayer and mencoder).

If I remember right, the reason mplayer was initially introduced was to provide thumbnails in Dolphin (or Konqueror? I can never keep the two straight). It wasn't for mencoder and I don't believe it was initially intended for a replacement/addition for xine, although it obviously works out that it can be.

Although, it should be noted that mpv is currently not supported as a phonon backend. I can't remember what the default is in Slackware (and if it isn't default, I don't know how many switch to it -- I think I initially did).

Slackware's default Phonon backend is gstreamer.

Originally Posted by bassmadrigal If I remember right, the reason mplayer was initially introduced was to provide thumbnails in Dolphin (or Konqueror? I can never keep the two straight). It wasn't for mencoder and I don't believe it was initially intended for a replacement/addition for xine, although it obviously works out that it can be.

MPlayer was added to Slackware, only so that Pat and I could enjoy the Electric Sheep screensaver.

Eric

Originally Posted by solarfields by me?

Yes. It shouldn't be hard to do so and unless Patrick already has a few on the way. If you need help, let us know. Get you hands dirty solar! It's fun!

Yes. It shouldn't be hard to do so and unless Patrick already has a few on the way. If you need help, let us know. Get you hands dirty solar! It's fun!

It is already done. Robby knows about it, so let's hope we see XFCE 4.12 in -current soon.

what it the problem with gcc 4.9.2, why is current still on 4.8.x ?

If it's out, then maybe Robby can look into it.

what it the problem with gcc 4.9.2, why is current still on 4.8.x ?

The latest is not always the greatest. gcc-4.9 is still getting significant patches. e.g. https://bugs.gentoo.org/show_bug.cgi?id=523326#c25

Originally Posted by allend The latest is not always the greatest. gcc-4.9 is still getting significant patches. e.g. https://bugs.gentoo.org/show_bug.cgi?id=523326#c25

hm, gcc is not the patch receiver in this cases .. but I am sure you understand this

So why is there a gcc 4.9 patch attachment on that thread?

Originally Posted by allend So why is there a gcc 4.9 patch attachment on that thread?

because it is patching the build (Makefile), not gcc it self.