Programs, what you like to see in Slackware tree
 

Hello! I want to know what we like to see in Slackware tree.
As for me, i want to see proxy server (maybe squid), jabber server (maybe openfire), and more another...

Hi,

I'm satisfied with Slackware as it comes. If something is needed then I just get what is needed at Slackbuilds.

Slackbuilds is a good source of packages, read the FAQ.

If not there then just build a package using the template from the source.

Plus you can always look at Alien_Bobs' Main Package Repository.

PV & Team do have to cut things off somewhere. That's why we have Slackbuilds to provide additional packages that are built by Slackware users for the Slackware community.

Yeah, but in Slackware tree many other servers, but there is no proxy and jabber for example, but there are yet two or more DHCP server...

I agree onebuck. Slackware ships with an excellent complement of programs. If I need additional applications I will peruse the above-mentioned links.
Also, rworkman provides excellent Slackware packages. Robby is one of our Slackware developers; his packages are also completely trustworthy.

rworkman's Slackware Packages

I would like to have ZIM preconfigured and -installed. ZIM is like a desktop-wiki. See http://zim-wiki.org/

gtkglextmm

It's requirement for VisualBoyAdvance Merge's GUI. I was unsuccessful in building it.

However, I agree that the argument for including Squid is weak when you can just pull it from SlackBuilds.org.

I'd like to have texlive instead of tetex which is not maintained anymore. So I use rlworkman's package.

I would like to have NetworkManager (wicd is good, but it lacks mobile broadband support which many users need nowadays).

This would be great, but I suspect it would take up too much room on the DVD.

I consider the two most important ones, a seperate xulrunner (maybe along with nss and nspr) instead of using seamonkey and libreoffice. Texlive would be nice too.
But the chances of seeing the later two any time soon are pretty slim, since their sources are huge.

fakeroot

The fakeroot program allows you to build packages without root privileges. If you make a mistake in writing a build script, you don't accidentally modify system files.

Hi,
If you just build a package no system files will be touched. If you are modifying a build script then do so from a copy of the original. If you are satisfied with the build then doing the installpkg will modify.

This reminded me an incident I had a few years ago, when I was working on some SlackBuild and accidentally left one variable undefined. The problem was the line below, something like rm -rf $FOO. Ended up losing almost all of my system partition, luckily my personal files were left intact.

That's why it's crucial to test those things in some sort of isolated environment. And have backups. :)

Best to build in a VM so we can have a pure environment; besides, safety issue solved.

I'd also like to see NetworkManager, at least in /extra.

Im with piratesmack, id also like to see NetworkManager, then i dont have to worry about wvdial. Extra would be fine.

I think Openbox would be a nice addition to the preinstalled WMs.

mono and systemd... but only after I've had my eyes clawed out by a rabid gerbil and then fed feet first through a chipper.

The kitchen sink.

LXDE and NetworkManager.

Just thought of another I'd like to see:
sbopkg

Again in /extra would be fine.

Happy with the say things are already, but for others....
 

I don't really have any requests for additional packages. SBo takes care of most of that for me, and what it doesn't, I can create my own packages.

But I listen around, and what I hear from a lot of people is that they like to deploy sudu Linux because their semi-computer-literate users or staff can have a familiar experience out of the box with apps that are akin in nature to what they're used to.

For me, I find that concept rather repulsive. If I want a wYNd0z3 like experience then I'll fire up wYNd0z3.

That having been said, two things come to mind:

• sbopkg
• LibreOffice

The first item, again, is a non-issue for me. I just go and get it as part of my standard setup.

The second item, would make things a bit more streamlined for those folks who feel that a potential Linux convert needs a "Familar" experience.

um...

Well wait a minute. Maybe I'd rather see Dovecot instead of UofW.

Yeah, I think I would prefer that.

Oh, and one more thing... I think we should dump MySQL and have MariaDB as part of the base instead.

The nice part about that is, that no one would even know it unless they looked under the hood - I despise EllisonCo.

I hope that helps :)

Kindest regards,

qtiplot
cuz it's a bitch to compile

has anyone out there successfully installed that? A link to a working slackbuild would be highly appreciated...

Dude!! Your eyes have feet?!

I agree on the inclusion of fakeroot. It prevents mistakes when working on your own SlackBuild scripts, since you aren't really root.

Also agree with the requests for sbopkg and network manager even if they only made it into extra.

Finally, if it does get to the stage where KDE is dropped then the components to create a nice LXDE desktop would be appreciated to give an alternative Desktop Environment to Xfce.

Oh ... And of course Opera! ;) Though I admit I am totally biased on this last point.

There was a thread like this shortly after the release of 13.1. Groundhog Day.

haha nice catch

Postfix and Dovecot would be nice. And I surely wouldn't complain about having PostgreSQL also.

But mostly I'm very pleased with the packages selected by the Slackware team. And as long as there's a slackbuild script to be found, I can just build the software myself. YAY! for slackbuilds.org and sbopkg. :)

NetworkManager

A bar and some lapdancers.

As many people pointed out, I would enjoy having NetworkManager on the Slackware tree as well, but I believe it will never happen due to the multitude of gnome libraries it takes.
I would also like Clementine instead of Amarok, but again, a shit ton of gnome libraries/audio plugins are required.

Most definitely networkmanager.

I'm sure most of us here realize that any wish list discussion places additional burden on the development team. Therefore I'm thinking only popular apps that are already supported in other repositories by members of the team.

Some possibilities:

LibreOffice (full build script, not just a deb conversion)
Squid
Wireshark
GParted
Possibly a graphical hardware inventory tool (LSHW?)
Replace Google Chrome build script with Chromium
LXDE
GTK app equivalents of KDE apps to help Xfce/LXDE become full-featured desktop environments

The /extra branch is a good place for all of these packages.

Every time I install Slackware on a different hardware I run lshw, so +1 for this. Great is the availability of different output methods (text, html, ...).


:hattip:

OpenLDAP server, something better than yp and NIS, which I am currently using.

I compile Qtiplot on slackware regularly since 2006.It works. But, from one Qtiplot release to another you often need to tweak qtiplot.pro/ other build configuration files. What's most annoying is the need to change default install locations of qtiplot plugins from /usr to /usr/local (/usr is actually hard coded).
I never tried to make a slackbuild for Qtiplot. May be I'll try to make one if/when I have time.

Okay, I managed to build it with this patch:

https://trac.macports.org/attachment...widget.cc.diff

I'm submit a SlackBuild to SBo tonight.

That would be great! An a nice addition to slackbuilds.org

LibreOffice

Gparted - it's difficult to install, because of requirement of newer versions of some libs and should recompile it...

partitionmanager is in extra/ and does the same thing.

I honestly can't understand the call for NetworkMangler. It's a
tool that comes with e.g., the *buntu family that is reason for
a great number of people posting on LQ about issues.


How odd ...

I'm happy with wicd even though it is no longer maintained.

I'm happy w/ vim ;}

Sure. Each to his own. I'm not averse to using a text editor for tasks. However, there is nothing wrong with using a GUI that works well. :)

respectfully submitted,

Sure wicd works ok with wireless networks but doesn't work with mobile broadband connections. With networkmanager you havean easy to setup all in one network tool ideal for laptops.

It is the first packages I download and install after an install on my laptop.

Though not a program per se, I am hoping that libunistring will find its way into the next version of Slackware.

Well since sbopkg is failing to update for me and I spend a good half hour chasing down dependencies to build nitrogen earlier, I'm gonna say umm nitrogen.

Yes, networkmananger does indeed look nice. I suspect it is not included yet because of the required dependency list. I will give networkmanager a look if wicd becomes flaky on my Acer netbook.

I particularly like claws-mail, it is quite full featured and does IMAP.