Hello,

All is ok on my side :

--
SeB

Thanks, everything is ok, with Your ".nl" URLs. Downloaded and updated

dosfstool-4.0 is available:

https://github.com/dosfstools/dosfstools/releases

https://github.com/dosfstools/dosfst...ols-4.0.tar.xz

I tried both ghostscript 9.18 and 9.19, and I could not reproduce the crash when gimp importing a PS file, does anyone have a valid PS/EPS file that will crash gimp ps import?

P.S tested with Slackware64-current on Dell Optiplex 390 with 8G of RAM.

I tested gs-9.19 back in March, and GIMP could not load testprinter.ps (easily found with a Google search).

I got it reproduce on 32-bit system, on 64-bit system, I have no error.

wavpack-4.80
http://www.wavpack.com/wavpack-4.80.0.tar.bz2

I suggest that slackware moves to netatalk 3.1.x now since 2.x is over 4 years old now and pretty much no longer works on El Capitan an later macs.

The config file is different, but it's much better in my opinion.

new file-5.27:

https://github.com/file/file/blob/master/ChangeLog

ftp://ftp.astron.com/pub/file/file-5.27.tar.gz

1 members found this post helpful.

it seem ghostscript since 9.12 version need this patch (ghostscript-sys-zlib.patch):

https://git.archlinux.org/svntogit/p...es/ghostscript

Just a thought, but could upx (ultimate packer for executables) be used with pkgtools to compress the binaries of distributed packages to save any disk space as well as reduce package size for downloads?

Hi,

It wasn't in the era of modems and small HHDs only, so why would it be used now?
Is there any speed gain?
Is the upx proven not to produce broken binaries?

--
Best regards,
Andrzej Telszewski

It works fine when I used it, just never tested on a mass scale.

At the rate new things, such as dependencies come into play, the size of Slackware has grown exponentially. We already push the limits of DVD 4.7GB media and /sources was pushed to it's own media disk.

It's not saving much, granted, but every little bit that keeps the size of the distribution manageable, in every way possible, is worth looking into. It might not help for small packages as it is, but what about larger ones?

Hi,

I'm not concerned too much with the download size. It's something you do once and then keep the copy.
And Slackware does not seem to be including any big piece of software anytime soon, so the size isn't going anywhere from where it is now. But hey, if it does not fit single DVD, then use two of them Although for me it's hard to judge, because I don't remember when was the last time I used DVD, some of my machines doesn't even have the DVD drive.

When it comes to upx my concerns are:
1) as I mentioned before, are the binaries reliable?
2) how long does it take to decompress binary? Especially the bigger ones?
3) can the RAM be reused by the same binaries or are they going to use separate memory areas?

I haven't dug into the topic, so my questions might have good answers, but that would be my concerns.

Nowadays we have plenty of storage, so reducing package size would mostly matter for modem users.
And I don't think they would care much if the difference was something like 500MB when you have to download almost 5GB.
I was a modem user once and I wouldn't care

--
Best regards,
Andrzej Telszewski

You don't actually decompress the binary. It runs as is.