You are sounding like a scratched vinyl record. Remember the warning from the forum moderators: in the Slackware forum, starting another flamewar about systemd can cause your account to be locked.

5 members found this post helpful.

This requires rust. I've been looking into rust, and have had some helpful emails with hints about how to proceed there. But I have to say that as much as it looks like using rust would be beneficial to Firefox security, it doesn't seem entirely ready for prime time. When a language that's written in itself can't compile itself without the use of a large bootstrapping compiler provided as binaries, there's work to be done.

There's also a new 52.1.0 ESR that I intended to put into -current until we know what to do about rust, but it doesn't compile. I'm looking into that, but won't let it block things.

11 members found this post helpful.

I'll just say that I looked into rust before, spent sometime adding simple things like --docdir to their extremely convoluted build system (Unintentionally breaking the build for platforms I don't have in the process...) and then I tried cargo which immediately started to download a whole bootstrapping environment during configure... Suffice to say I dropped the idea quickly.

5 members found this post helpful.

Talking about Rust, I wonder if GCC could be compiled with no C/C++ compiler present in the system, at all...

Maybe the issue is just that Slackware does not ship yet a Rust Compiler?

1 members found this post helpful.

Why would Patrick say "it doesn't seem entirely ready for prime time" if the issue were actually the lack of a Rust compiler? O_o

A Rust compiler is available for Slackware anyway, so that's not it:

https://slackbuilds.org/repository/1...elopment/rust/

2 members found this post helpful.

compiz-0.8.14
https://github.com/compiz-reloaded/compiz/releases

Looks like the compiz-reloaded team just pushed 0.8.14 releases for the entire set of compiz packages. It would be nice to see compiz dropped from the main tree and turned over to SBo so that it would be easier to keep all the packages together. If not then a nice alternative would be to see the 6 year old 0.8.8 release upgraded to the newest version. The compiz-reloaded project has been around for a while now and most distro repos are adopting their releases over the old now defunct compiz.org packages.

A few pages back I requested that freetype be updated to 2.7.1. The reason why I would like to see this is because the 2.7 branch of freetype now enables subpixel-hinting in the default build. This is particularly nice because the freetype slackbuild has a patch to enable subpixel-rendering and when freetype is rebuilt with subpixel-rendering and subpixel-hinting enabled you can get infinality level of rendering quality simply by symlinking the appropriate entries into your /etc/fonts/conf.d.

Right now current has freetype 2.6.5 which has support for subpixel-hinting, but it is disabled by default. I can see Pat sticking with 2.6.5 so that the sudden change in font rendering you would get with 2.7 won't bother people. However, if possible, it would be great to see a patch to enable subpixel-hinting in the slackbuild like there is for subpixel-rendering. That way for those of us who recompile freetype we can get both of those options enabled easily instead of having to edit the slackbuild with sed or a custom patch to enable subpixel-hinting.

1 members found this post helpful.

Wondering if you noticed that our glorious SlackBuild for Rust use initially a large bootstrapping compiler provided as binaries...

Support for NPAPI plugins (other than Adobe Flash) has been removed.

This has already happened in Firefox 52 (not ESR). See https://www.mozilla.org/en-US/firefo.../releasenotes/. Firefox 52 ESR is the last version to fully support NPAPI plugins.

2 members found this post helpful.

As audriusk pointed out, this was done in version 52.
You might want to check the links in message #2018, on page #70, of this thread (topic).

Are you unfamiliar with bootstrapping a compiler, Darth?

A closer analogy would be to imagine that you have GCC on the machine, and you're able to compile things. But you can't compile GCC with it.

I've had rust installed here, BTW.

3 members found this post helpful.

I am familiar with bootstrapping a compiler, of course.

But, looks like I had understand wrong which issue is...

Surely, I agree that the Rust compiler not being able to re-compile itself is a really nasty issue.

2 members found this post helpful.

Just a friendly reminder that /etc/ld.so.conf points to an inexistent directory on Slackware64. It points to /usr/x86_64-slackware-linux/lib/, but the a/binutils package creates a symlink of /usr/x86_64-slackware-linux/lib64/ (pointing to /usr/lib64/ldscripts/), following the ${LIBDIRSUFFIX} variable used in the etc.SlackBuild. The a/etc package creates ld.so.conf, and while I'm sure the etc.SlackBuild's sed line could be changed to keep the lib directory at the end (instead of lib${LIBDIRSUFFIX}, it seems like the easier option would be to adjust binutils.SlackBuild to use the ${LIBDIRSUFFIX} variable when creating that symlink.

Here's a quick patch I created when I previously posted about this.

As mentioned before, I doubt this is a big deal as it's just a symlink, and the linked directory is listed before this one in ld.so.conf, but it'd still probably be a good idea to have it point to the correct directories

4 members found this post helpful.

I thank you for this post; it got me to look into freetype's latest release, and came across the sed patch to enable subpixel hinting. I've got to admit that the fonts look ever so much better now. Thanks again!

1 members found this post helpful.