Hello all,

I have a few Slack systems of my own now and tend to build and rebuild some in my lab. Can I setup my own Slackpkg mirror to grab all the updates on one system then point the rest of mine to that central system?
I want to be able to download updates on one then blacklist any one time then apply the rest to my other systems. For example currently the Samba update breaks the OwnCloud client from Slackbuilds so I can't update it until a fix it found. I want to be able to blacklist it on my central server so I don't have to on all the rest.
I'd also like to be able to stick a couple packages I've made from Slackbuilds into my slackpkg server.
The slackbuild doc section for mirroring takes me to the Slackware web site where you setup public mirrors so thats not quite what I want.

Is there really no write up about this.

http://www.linuxquestions.org/questi...re-4175511066/

Edit: Have a look at the posts by me

I think Slackpkg+ would do what you want to accomplish. That is how AlienBob manages his packages. Check his blog entry if this is what you need :-

http://alien.slackbook.org/blog/intr...-repositories/

Regards.

You can have a local mirror of Slackware and point your local machines at it, that part is easy. For 14.1, find a Slackware mirror that supports rsync (there are lots of them, once it's set up you only need to rsync patches/ regularly). For -current, use Eric's script -> http://www.slackware.com/~alien/tool...are-current.sh

Either you could use something like rdist to distribute /etc/slackpkg/blacklist to all the local machines (you would have to update /etc/slackpkg/mirrors on all the local machines to point to your local repository, so you might as well do both files at the same time);

or you could replace the version of Samba on your local mirror with the old version, but that would break the manifest and checksums and signing of the whole mirror, so it's a bad idea.

But this is a *very* rare situation, which is why there is no established way of doing it. Also, the Samba update is a security fix; you really don't want to skip it.

By far the best solution is to solve your owncloud-client problem. I've got a SlackBuild for the latest Owncloud client here -> https://github.com/idlemoor/unoffici...wncloud-client
It depends on the latest qtkeychain which is here -> https://github.com/idlemoor/unoffici...SBo/qtkeychain

And if you want to set up a central repository of local SlackBuilds for multiple local systems, have a look here -> http://idlemoor.github.io/slackrepo/ and use it with slackpkg+ as PrinceCruise suggested.

Hi,

Here's how I do that :

Like 55020 said, you must find a rsync capable mirror.

Then run a full rsync sync in whatever directory you want.

I personally don't have a use for the source directory so it's not rsync'd on my server.

Install a web server (e.g Apache in my case) and do this :

(Yes, I know it's kinda "dirty" so be careful with that advice especially in a production environement ! )

Create a symlink in /var/www that goes to your Slack "rsync'd" mirror and restart your web server.

Finally add your repo in /etc/slackpkg/mirrors

Where slack-repo is the name of your symlink.

My Slack repo "machine" is a Rasperry Pi.

As you can see, you don't need a powerful machine to achieve that.

I also use http protocol instead of file since it's a lot faster and can be used for my VMs as well

I downloaded eric's script but its looking like its a lot more work. I was hoping I could just share the new packages that slackpkg downloaded on one server then point the others to it but it appears I have to rsync a whole install.

55020, I'd love to get a newer OC client running but I seem to be unable to get your slackbuilds to work, they keep looking for the old version. My be just my lack of knowledge of git.

you can start off by extracting Slackware's DVD to minimize download effort

May be? You don't have to go anywhere near git.

For qtkeychain, you don't really need to change the existing SlackBuild at all. Just download the new source for version 0.3.0 and run the SlackBuild with
For owncloud-client, only the SlackBuild and info have changes, so there are only two files to download. Here are direct links:
owncloud-client: owncloud-client.SlackBuild owncloud-client.info

Sorry. just getting back to this. The odd thing was when I downloaded that slackbuild from github and ran it, it kept asking for the older OC client.

NEway: Here's what I'm doing. I've added an additional system at home running Slack and its a media center pc (running xbmc). So at the moment I have to ssh into it, my laptop, and my server and update slackpkg then upgrade all. Not too big of a deal yet. But I'm adding another system for my son to upgrade his laptop. Hoping to keep it Slack too instead of windows. So in addition to keeping Slackpkg up to date I'd like to be able to have addiitonal software such as Libreoffice or a couple games. So I can just update the LibreOffice packages on my local slackbuild repo and then when I run the slackpkg update on each other system it will see those new libreoffice packages.

I have my own Slackware repository here:

http://www.microlinux.fr/slackware/

To create the metadata, I'm using Eric Hameleers' gen_repos_files.sh script:

http://www.slackware.com/~alien/tools/

To manage packages, I'm using the slackpkg+ plugin.

Getting everything to work was a bit tricky at first, but I got much help from Eric on IRC and here on LQ. Once everything's up and running, you wouldn't want to go back. I'm managing a few Slackware servers and desktops, and my workflow has become much more efficient using my own repo.

Cheers,

Niki