As per subject line I have a remote slack web server still running 8.l.
I'm presuming that since 10 is out it will soon be dropped from the list
of versions for which Pat releases binary patches. (though i noticed it
got the recent PHP patch along with the newer versions).

Given that it's remote, what's my best strategy for keeping at least core
applications (apache php etc.) up to date? I tried googling for
"slackbuild" since I recall that it may be possible to download the
source and use Pat's slackbuild scripts on an old box to keep it up to
date. Didn't find anything exactly like my question. Am I on the right
track with that idea? Yes? No? Maybe so? Any help much appreciated.

Moss Hart




-----= Posted via Newsfeeds.Com, Uncensored Usenet News =-----
http://www.newsfeeds.com - The #1 Newsgroup Service in the World!
-----== Over 100,000 Newsgroups - 19 Different Servers! =-----

Moss Hart wrote:

> As per subject line I have a remote slack web server still running 8.l.
> I'm presuming that since 10 is out it will soon be dropped from the list
> of versions for which Pat releases binary patches. (though i noticed it
> got the recent PHP patch along with the newer versions).
>
> Given that it's remote, what's my best strategy for keeping at least core
> applications (apache php etc.) up to date? I tried googling for
> "slackbuild" since I recall that it may be possible to download the
> source and use Pat's slackbuild scripts on an old box to keep it up to
> date. Didn't find anything exactly like my question. Am I on the right
> track with that idea? Yes? No? Maybe so? Any help much appreciated.

During a conversation with him minutes before 10.0 was released, he
mentioned that he'll keep 8.1 around for awhile. However, I wouldn't count
on it to survive too many new slack releases, possibly one more. However, a
good way to update it would be to use the slackbuild scripts. Go on any
slackware mirror, under
slackware-8.1/source/disksetnamehere/packagenamehere. In there you will
find source tarball of the software, slack package description and a small
bash script. In most cases all you have to do is replace the source file
with whatever new version, and edit the bash script to point to the new
version. Then run the script, and a new package will be placed in /tmp dir.

This of course is a generalization, some packages contain small patches. It
varies, so be sure to read what the script actually does.

Last but not least, consider upgrading to a newer slack.

[ohh, and yes, you're on the right track, if you have the time to do that]

Moss Hart wrote :

> I tried googling for "slackbuild" since I recall that it may be
> possible to download the source and use Pat's slackbuild scripts on
> an old box to keep it up to date.

Check out any Slackware mirror, you'll find P.V.'s build scripts in the
/source directory.

Creating a local clone of the remote server is a great idea. Build and
test the package here and then upload the package to the remote server
and install.
--
Thomas O.

This area is designed to become quite warm during normal operation.

Moss Hart wrote:

> As per subject line I have a remote slack web server still running 8.l.
> I'm presuming that since 10 is out it will soon be dropped from the list
> of versions for which Pat releases binary patches. (though i noticed it
> got the recent PHP patch along with the newer versions).
>
> Given that it's remote, what's my best strategy for keeping at least core
> applications (apache php etc.) up to date? I tried googling for
> "slackbuild" since I recall that it may be possible to download the
> source and use Pat's slackbuild scripts on an old box to keep it up to
> date. Didn't find anything exactly like my question. Am I on the right
> track with that idea? Yes? No? Maybe so? Any help much appreciated.

I have my entire server rack as Slack 8.1 but most of my stuff is compiled
from source. I rarely follow packages anymore only because I get impatient
in waiting for them to be released.

Nevertheless, I have resorted to making my own packages with a nice utility
(shameless plug here) called check_install. It is package-neutral - it
will make packages for Slack, RedHat RPM and Debiant apt.

--
<Petter>It's a bug
<X-Winger2>I refuse to believe XP has any bugs ;P
<X-Winger2>well
<X-Winger2>Except it won't let me see my hard drive right now

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

In alt.os.linux.slackware, WarpKat dared to utter,
> Nevertheless, I have resorted to making my own packages with a nice utility
> (shameless plug here) called check_install. It is package-neutral - it
> will make packages for Slack, RedHat RPM and Debiant apt.

If you're using the package nuetral version you should know that it
makes broken Slackware packages because it doesn't use the correct tar
version (1.13). There's official Slackware packages in /extra on 9.1
and 10.0 for a Pat V patched checkinstall that's flawless at making
Slackware packages, but doesn't make debs or rpms.

- --
It is better to hear the rebuke of the wise,
Than for a man to hear the song of fools.
Ecclesiastes 7:5
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQFBBaVTlKR45I6cfKARAvF3AJ9sfswTlO+zvrvvQuJvAo Z59+fKhgCfeIzw
3QDIYqnez1kXJJPIeSHu6w4=
=PJy0
-----END PGP SIGNATURE-----

Alan Hicks <alan@lizella.network> wrote:
> > [check_install]

> If you're using the package nuetral version you should know that it
> makes broken Slackware packages because it doesn't use the correct tar
> version (1.13). There's official Slackware packages in /extra on 9.1
> and 10.0 for a Pat V patched checkinstall that's flawless at making
> Slackware packages, but doesn't make debs or rpms.

Having looked at the source for checkinstall 1.5.1, it doesn't
appear to have built-in source for tar; indeed it just seems
to call the system tar from the checkinstall script.

It might not make perfect Slackware packages, but I don't see
how it can be using the wrong version of tar.

#Paul

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

In alt.os.linux.slackware, kinslerp@delillo.lsr.ph.ic.ac.uk dared to utter,
> It might not make perfect Slackware packages, but I don't see
> how it can be using the wrong version of tar.

# grep tar /sbin/installpkg
TAR=tar-1.13

Out put was snipped.

- --
It is better to hear the rebuke of the wise,
Than for a man to hear the song of fools.
Ecclesiastes 7:5
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQFBBvXqlKR45I6cfKARAnCEAJ9+cYFIBplbH4F7FLeghq TTBV/alACdEWQB
hN753uFkRa4aXIIyAMRGa1w=
=cyCG
-----END PGP SIGNATURE-----