httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jim Jagielski <>
Subject Re: Signatures, and sealing wax, and..
Date Tue, 12 Aug 1997 19:24:13 GMT
Brian Behlendorf wrote:
> Those two, plus dbm_auth, anon_auth, expires, headers, and setenvif.  The
> last one in particular since we have to provide lines to make sure broken
> browsers still work.

They make sense to add.

> I'd like to dump "compress", personally.

I'd +1 that...

> As mentioned, not all binary builders will have access to PGP or an MD5
> tool.  Though those do exist on hyperreal, so anyone with an account
> uploading their own builds to there (or handling one from a trusted source)
> could handle that.  Making is a suggestion and not a requirement is preferred.
> >    5. src/Configuration should use the platform's native cc(1) if it's
> >       considered good, and *not* gcc - unless the native cc is suspect
> >       or downright broken (HP-UX, can you hear me calling? ;-).
> This should be up to the binary builder, in my opinion.
> Should we recommend a level of optimization used?  I.e. if gcc, use -O2?

If it works :)

      Jim Jagielski            |       jaguNET Access Services           |
            "Look at me! I'm wearing a cardboard belt!"

View raw message