From: Jim Jagielski <jim@jaguNET.com>
Message-Id: <199708121924.PAA13372@devsys.jaguNET.com>
Subject: Re: Signatures, and sealing wax, and..
To: new-httpd@apache.org
Date: Tue, 12 Aug 1997 15:24:13 -0400 (EDT)
In-Reply-To: <3.0.3.32.19970812121928.0089e100@localhost> from "Brian
 Behlendorf" at Aug 12, 97 12:19:28 pm
Content-Type: text
Sender: new-httpd-owner@apache.org
Precedence: bulk
Reply-To: new-httpd@apache.org

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
     jim@jaguNET.com           |       http://www.jaguNET.com/
            "Look at me! I'm wearing a cardboard belt!"