How about beer and vodka?

You should use a wine.Slackbuild either from Alien Bob or slackbuilds.org or src2pkg to build wine, they all make it trivial to build.

You sure you're not Scottish?

samac

Referring to this?

http://news.bbc.co.uk/1/hi/scotland/8463333.stm

Is that with whisky chasers?

Yes, to both!

samac

Hrmmm... something for /extra. Being that slackware already has well maintained services, why is it that there is no UPnP server in slackware? Perhaps because UPnP is designed more for a user based daemon and not a system level daemon?

MediaTomb would be a nice choice but may clash with people trying to install MythTV.

If it weren't for the dependencies, I would also vote for Inkscape.

xmms2 seems interesting enough to go in slackware extras.

I'm close to saying blender... but the way it's designed to run, installing it system wide poses problems for users that like to install plugins and scripts and still want all the default ones available. Blender also seems to fall into the category of OK to use PreBuilt Binaries as they are "The way the author intended it"

Quite a lot of stuff from a/, ap/, d/, & xap/ & all of e/, f/, kdei/, t/, tcl/, & y/.

True, but then again that wouldn't be /extra, that would be /same-but-in-a-different-place.

samac

It all depends on your needs. For example brltty isnt an extra for blind people either.
And there probably are more blind people using Slackware, than the ones using the multimedia packages in ap/.

All of the above. Slackware is long overdue to provide an official central repository with precompiled packages.

Long overdue.

Why not? In another thread I asked whether sr2pkg can perform that particular feat. As explained to me, that is not a sound idea. Nonetheless, the comparative lack of prebuilt packages always has been noted by reviewers and one reason why some users stay away from Slackware.

There are logisitics to answer such as where to host a central repository, how to finance, who will support the effort, etc. Those are secondary issues that can be resolved. After all, there are many people now who build packages or at least support build scripts, and several who host packages at their own web site. Thus, the human energy and money is already available but not channeled into one location.

Adopt a common build script template and start moving all packages from all respositories to a central location. Would look nice too if the stock Slackware slackbuild scripts used the same template. Standards can be useful when used correctly.

The stock Slackware provides a nice foundation for a computer operating system. Missing is the many additional apps that many people want installed. No development team can support that amount of packages, but a community effort, sanctioned officially, tunnels all that same current effort into one location.

Actually, a centralized location is unimportant. What is needed is official sanctioning of third party packages and the ready availability of prebuilt packages.

The important point is Slackware is long overdue to provide an official large-scale central repository.

If this was possible it would be very good idea. Agreed. Even getting all the slackbuilds in one place would be a great start eg. Alien Bob and RWorkman both have their own repositories of slackbuilds, wouldn't that be better on slackbuilds.org Couldn't have said it better myself.

samac