richard

I am getting the same thing on 10.0 as well. I guess I am going to
have to roll my own from scratch...

How hard is it to create a new tgz package that "looks" like the
official tgz but includes mod_perl? I would like to avoid doing this
over and over in the future and creating a package to share with the
world would solve this problem for me (and possibly others). I have
never created a Slackware package before, but I assume that it's
doable; especially if I get the original build package script. Right?
:/

Thanx!
Richard

+alan hicks+

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

In alt.os.linux.slackware, Richard dared to utter,

That shouldn't be hard at all really. Just read the directions for
mod_perl and look at the SlackBuild script for apache (assuming there
is one).

Incidently I just set down today to look at adding mod_perl to apache,
but I'd like to do it as a DSO and make mod_perl it's own package ah la
mod_ssl. The instructions for building mod_perl and apache aren't very
helpful for making a DSO though. We're getting a little OT here. Anyone
ever made a mod_perl pacakge as a DSO?

- --
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)

iD8DBQFBYyOplKR45I6cfKARAnXpAJ9sms8Se2NZA25NKX8edb o+MwJHpwCfdjoW
QTzuT3io0P4IxCeN9kvpsSs=
=Lx9h
-----END PGP SIGNATURE-----

+alan hicks+

NOTE: This message was sent thru a mail2news gateway.
No effort was made to verify the identity of the sender.
--------------------------------------------------------

pgp trash troll delete

Hicks, Alan
188 Shady Dale Dr
Lizella, GA 31052
478-935-8132

hangaber

Tonight, I attempted to recreate a slackware package for apache, but with
suEXEC enabled. I too had never created my own package, and jumped in
almost blindly with a large amount of success!

From the 4th slackware CD, I copied the files from /source/n/apache/ (one
of the files was 0 bytes, probably a link to the same filename in
/source/n/mod_ssl/, so I copied that file over instead.)

[The link would have probably worked if I wasn't copying the files off the
CD using winderz. Yeah yeah, sorry but I was doing this remotely and
couldn't jump on a slack OS at the time ;]

I edited the file: apache.SlackBuild, adjusting the ./configure line for
the apache part.

I executed apache.SlackBuild.

The package had been created in /tmp ... I installed it (first backing up
config files, and uninstalling my old apache. I later deleted the related
dirs/files in /tmp).

The package installation went perfect. The only additional thing that I
needed to do, was a "chmod" that didn't automatically get done (it seems
the setuid didn't get copied or stored in to the tgz.... a chmod 4711. I
think I could have edited the script in /package-apache/install/ to do this
for me.)


I was very pleased with this. In the past, I had removed the slack
package, and just compiled + installed apache using a standard
../configure;make;checkinstall method, but the downside being that it was
tricky to have ALL the files install in EXACTLY the same place the slack
package would put them in.

Now if I want to enable SMTP AUTH with sendmail, or tweak fetchmail, etc...
I can rebuild my own slack package.

I'm no slack expert (this is my first post in to a.o.l.s) and there may be
"better" ways to do the above, but I hope this info helps you anyway! :]

(Oh, to enable mod_perl on the apache configure/make, ... I assume you know
how to do that part
--
+ Message has been scanned for vir//
//
//
Hard drive format complete.
PRESS ANY KEY TO CONTINUE