Seeking versioned repository of slackware64-current

ttk · 09-11-2013, 12:53 PM

A few months ago I started keeping a fully-versioned repository of slackware64-current, but too late to catch the Slackbuild for firefox-16.0.2.

I've googled around, and the closest I can find is this:
http://slackware.bokxing-it.nl/mirro...zilla-firefox/

.. which has all of the versions of the firefox source going back to 15.0.1, but has only the most recent version of mozilla-firefox.SlackBuild.

Does anyone know if such a repository exists somewhere? Or, at least, the version of mozilla-firefox.SlackBuild which worked with firefox-16.0.2?

Skaperen · 09-15-2013, 03:22 PM

Maybe this one from my collection might be the right one. If not, let me know and I can look around more as I have others. But this one was present at the time the 16.0.2 source came out. Ignore the date stamp in the NAME of the file inside the tarball since that is the data it moved to archive in my collection. See the meta timestamp instead.

http://phil.ipal.net/2012-10-09-mozi...ckBuild.tar.xz

Didier Spaier · 09-15-2013, 04:03 PM

mozilla-firefox being a moving target it seems that Pat avoided the hassle of updating VERSION every time:

Code:

VERSION=$(basename $(ls firefox-*.tar.bz2 | cut -d - -f 2 | rev | cut -f 3- -d . | rev) .source)
RELEASEVER=$(echo $VERSION | cut -f 1 -d r | cut -f 1 -d b)
# With esr releases we need to fix this
if [ "${RELEASEVER}r" = "$VERSION" ]; then
  RELEASEVER=$(echo $RELEASEVER | cut -f 1 -d e)
  RELEASEVERMAJ=$(echo $RELEASEVER | cut -f 1 -d .)
fi

So I think that you just need to replace the source tarball by the one you want and run the current script, that has probably not changed.

BTW looking at the script I see that localizing the package is provided. Nice!

Skaperen · 09-15-2013, 04:32 PM

This scripts have changed over time, but not for every version. Why the changes I do not know. I do not know if it is because of changes in the source, or changes in Slackware, or just improvements in the script. I do have a few of them going back in my incremental mirror. When a file is replaced by a different one, or deleted, my mirror script keeps a backup based on date when the backup was made.