Offering binaries for other hardware (fwd)

[Rob Hartill <ro...@imdb.com>]

Do we trust external binaries ? it sounds too dangerous to be
worth the risk.

---------- Forwarded message ----------
Date: Tue, 17 Jun 1997 15:15:37 +0200
From: Allan Marillier <al...@datasoft.co.za>
To: apache-bugs@apache.org
Subject: Offering binaries for other hardware

Hi - I have downloaded source for Apache 1.2.0, and compiled it on HP-UX
9.0
using GCC 2.7.2, as well as on DG-UX 5.4.2. It's very easy - but I know
some people do prefer to have access to binaries rather than compile
their own.

If you're interested (and of course if you feel that I am trustworthy,
or have
some means to check the compiled code !) I'm happy to provide binaries
for these
platforms whenever there are new releases. I also have access to a
number of
HP-UX 10.01, 10.10, and 10.20 systems, as well as AIX 3.2.5, 4.1.4,
4.1.5 and 4.20
if ever you have a need for them.

-- 
Allan Marillier
allanm@datasoft.co.za
http://www.datasoft.co.za/~allanm

Re: Offering binaries for other hardware (fwd)

[Brian Behlendorf <br...@organic.com>]

At 11:04 PM 6/17/97 -0500, Randy Terbush wrote:
>My first reaction is no. Do we have some liability for damages 
>caused by binary distributions? Does our LICENSE protect us 
>sufficiently from this?

 * THIS SOFTWARE IS PROVIDED BY THE APACHE GROUP ``AS IS'' AND ANY
 * EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
 * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
 * PURPOSE ARE DISCLAIMED.  IN NO EVENT SHALL THE APACHE GROUP OR
 * ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
 * SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
 * NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
 * LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
 * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
 * STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
 * ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED
 * OF THE POSSIBILITY OF SUCH DAMAGE.

I'd say it does. Should we add a bit about not using it to run nuclear
devices?  :)  www.pentagon.mil apparently thinks it's secure enough.

I have little concern putting it under /dist/binaries so long as the
compiler's name & email address is handy.  

	Brian
--=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=--
brian@organic.com          http://www.apache.org          brian@hyperreal.com