+1

Surely there is some one with super mod powers to correct it?

Slackware is actually pretty good, but answering the title:

Gparted

PeaZip

Python 3


some Python and Perl modules

I learned how to build packages and I would like to contribute doing some (i builded almost the whole backtrack set of tools with the proper configuration, gnome 3.7 and more), actually I ask myself why is the community not help Slackware doing so.

So many fans and followers... and yet a very small number of helpers. I could offer a hosting if a group would be willing to go on with me. I think we could do that in a way we would have several packages, in an organized way, listing and pointing to dependencies, a semantic and trustworthy source, but for that we needed the ones next to god on the game...

Hummm?

Seems to me that you totally missed SlackBuilds.org, a place where build scripts for common software is hosted.

Nein, I did not miss that, it helps a lot and I really appreciate what they did, after all i learned by editing their scripts to my needs, but when I look at Arch's website, I feel like it is missing something on Slackbuild, probably more contribution, maybe a more semantic design and sure a more updated repository.

I think a central binary packages repository would be great.
If your project come to reality and you need help with packaging, let me know.

how about file-roller in XAP? Would be nice to have a KDE-independent archive manager...

Thanks! and yes any help would be welcome if we would have at least 10 or 15 in a team, this project would be probably easier to carry on.

If you are going to use SlackBuilds.org scripts for that, then please read http://slackbuilds.org/faq/#package_repos first.

Eric

Eric, the idea is not just copy the SBo scripts and start using it.

But get a team with trusted people that are interested in making a large repository with trusted and tested scripts, all with md5, hash and private keys of course. The big issue is the determination and perseverance in such projects, but I think when other community can, we should be able too, but only will is not enough.

I did my own scripts reading the slackwiki.com and before that i compiled a lot from source, at least on this topic I know what I'm doing

I also did a script to create txz from .deb, but this is another adventure.

Do I understand you right, you don't want just to maintain a binary repository, but also a script repository with your own scripts? That doesn't make much sense to me, I would think the right approach would be to contribute your scripts to SlackBuilds.org, you can still use them to make binary packages. Why doubling the effort?

Not exactly doubling the effort from my point of view.

They have their rules and so. I would like to have it in another way. and a team of slackers that could deliver trusted scripts more frequently.

3 members found this post helpful.

This seems appropriate. Perhaps you should check out slacky.eu which has its own repository of scripts and binary packages (and has for some time). The 14.0 tree is a little bare at the moment though.

2 members found this post helpful.

I've had little trouble finding the packages I want when I want them. Blender3D is very nice, but so is LibreOffice, Scribus, Inkscape Font Forge and a lot of other packages that a lot of folks would never use...

Google AlienBob to find his package repository, and if he doesn't have it, slacky probably does. That's where I went for ocaml ... I like this little programming language a lot, but no, I do not think it should be in the standard distribution.

I'd like to see Guile upgraded to include all the new capabilities of the 2.0 line, but there doesn't seem to be much interest, so I get to learn to make my own packages...

I find KDE to be a Royal Pain because it writes huge configuration files and directories into my /home/user directory where I really can't spare the space (and I don't have the RAM to support it properly either)...so I use xfce, but I still use a lot of the KDE apps. Kstars is critical for my peace of mind.

I'd like to know I have system-wide UTF-8 support and I'm concerned when I hear elvis doesn't have it.

Other that that, I'm perfectly happy with Slackware just as it is...

Thanks again, Pat!

It is unlikely that you, as an unknown newbie to the forum here, who has not yet produced anything and for unspecified reasons is apparently unwilling to work with SlackBuilds.org (a perfectly good, well-managed, and already existing project) will be gaining my trust any time soon. Whether you gain anyone else's remains to be seen.

5 members found this post helpful.