we did. it was sweet.

2 members found this post helpful.

I think the key package that is missing from Slackware is sbopkg.

I would love to see it either installed by default or as part of /extra .

9 members found this post helpful.

I would personally like opus and opus-tools to be brought in and supported. I like using it for some music, and it seems to be something that will be around for a while. Also, the packages needed are quite small:
PS: Including sbopkg in /extra would be awesome!

+1 for sbopkg.

Wikipedia states that it has been superseded by Shaman2, but I can't find the code for that anywhere.

Edit: Looks like it's here:

Edit #2:

It seems like it doesn't support pkgtools anymore:

Oh, and please please please please please:

• mozilla-firefox-langpack
• mozilla-thunderbird-langpack
• seamonkey-langpack

These are not only tedious to build, but they also have to be perfectly in sync with every released version.

3 members found this post helpful.

I of course second that. Maybe kdei/ could be renamed like intl/ or l9n/ or localization/, whatever, and these packages put there? Else in extra/, as aspell-words-lists/?

5 members found this post helpful.

IMHO, building those language packages for all the Slackware versions that receive updates with the frequency mozilla-suite new/bug-fix versions come out (that is so different from the one kde -or aspell- is updated in -current) could be really painful (that is one of the reasons why some time ago I sent Pat a patch to modify the firefox SlackBuild to allow the possibility to self-build an already localized package if someone got the need for it).

That patch was incorporated into Slackware 14.1. From mozilla-firefox.SlackBuild:

Well done.

Eric

Cool, nicely done.

You could also use my latest-firefox script and repackage the prebuilt localised binary that Mozilla offer, e.g. to get an Italian version:

If want another language you could choose to set FFLANG to any one of the following: ach, af, ak, ar, as, ast, be, bg, bn-BD, bn-IN, br, bs, ca, cs, csb, cy, da, de, el, en-GB, en-US, en-ZA, eo, es-AR, es-CL, es-ES, es-MX, et, eu, fa, ff, fi, fr, fy-NL, ga-IE, gd, gl, gu-IN, he, hi-IN, hr, hu, hy-AM, id, is, it, ja, kk, km, kn, ko, ku, lg, lij, lt, lv, mai, mk, ml, mr, nb-NO, nl, nn-NO, nso, or, pa-IN, pl, pt-BR, pt-PT, rm, ro, ru, si, sk, sl, son, sq, sr, sv-SE, ta-LK, ta, te, th, tr, uk, vi, xpi, zh-CN, zh-TW, zu.

I did a quick test on my Linode instance. It took me approximately 24 seconds (including fetching the build from Mozilla servers) to repackage of Firefox 31.0.

My case might not be representative here, but I have to manage three different languages for my users here: french, english and german. Localized builds are of little to no interest here. At the moment, I have to build mozilla-firefox-l10n-{fr,de} for every updated version.

While it would be nice to be able to upgrade the language packs via one's favorite package manager, I must say I did something stupid and tried writing a script for this that actually seems to work. I had a look at Archlinux' PKGBUILD and ruario's latest-firefox script to get an idea. The script will auto-detect the firefox (-f for firefox, omit for thunderbird) or thunderbird version installed (-v to override), get the language from LANG (-l lang-code to override this) and create a package out of it (if -p is specified; the package creation was added later, at first it just downloaded the xpi into the current directory). So I run prog -f -l fr -p to create a french firefox language pack for the currently installed version. I have tested this with firefox from ruario's latest-firefox and Slackware's thunderbird over several versions.

So if it's too much of a hassle I will continue using my script. No idea if it's worth sharing, I see kikinovak has his own SlackBuilds and ruario has his latest-firefox script, so there does not seem to be any demand.

What I would like to see, though, is translations for k3b. I don't know if it's still true, but last time I checked k3b was in english still. There was a thread about this a while back.

1 members found this post helpful.

dmenu - it's small, useful and mature; a good fit with Slackware, IMO. There isn't really anything in Slackware at present that does what it can do.

slackpkg+ would be a good addition in /extra too (I haven't used sbopkg, as my limited SBo needs are met by the Slackbuilds scripts, but I appreciate the easy access to repos like AlienBob's for bigger programs like libreoffice and calibre that slackpkg+ gives)

IMHO, if possible, remove - upowerd, the whole 'blueman/bluetooth' thing (are there really that many people who use it? Not a sarcastic question, just an honest one), Dolphin, Dolphin, Dolphin (yeah, I know, it's part of KDE, but it sucks and is a resource hog!!), neposuck (or at least have it turned *OFF* at install instead of ON as it is now), FVWM, probably a bunch of other stuff but that's all I can think of for now.

Add - LXQT (and thus qt5), libjpeg-turbo (as opposed to libjpeg), krusader (as default file manager), vlc