Oops. I realised this after I sent it and read the spec file. However, I
note that the spec file that is on the modssl site now is not the same file
as that included in the source rpm.
Could it be possible to put each spec file used for each version on the ftp
site, as is done for openssl? That way you can download the source ,edit the
spec file for example to include the SSL_EXPERIMENTAL code and build your
own source RPM. I've had to do that several times, just to get the
ssl-engine code working.
Thank you again for your help.
-
John Airey
Internet Systems Support Officer, ITCSD, Royal National Institute for the
Blind,
Bakewell Road, Peterborough PE2 6XU,
Tel.: +44 (0) 1733 375299 Fax: +44 (0) 1733 370848 [EMAIL PROTECTED]
> -----Original Message-----
> From: ModSSL user [mailto:[EMAIL PROTECTED]]
> Sent: 29 March 2001 14:57
> To: [EMAIL PROTECTED]
> Subject: RE: Latest RPMs for mod_ssl
>
>
> >Thanks for doing this guys. Could I be a little pedantic and
> suggest that
> >the manual should probably be a "noarch.rpm" rather than a
> "i386.rpm"?
> >AFAIK the manual is processor independent
>
> A known feature (limitation) of rpm.
>
> You couldn't generate in the same .spec a noarch RPM and
> arch (ex: i386)
> RPMs.
>
> So to have a .noarch RPM you need to use a second .spec which in turn
> give you a second SRPM which also contains apache sources....
______________________________________________________________________
Apache Interface to OpenSSL (mod_ssl) www.modssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
