Re: 7.2 items - Mailing list pgsql-hackers

From Patrick Welche
Subject Re: 7.2 items
Date
Msg-id 20010514211815.B11611@quartz.newn.cam.ac.uk
Whole thread Raw
In response to Re: 7.2 items  (Peter Eisentraut <peter_e@gmx.net>)
Responses Re: 7.2 items  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-hackers
On Mon, May 14, 2001 at 09:36:56PM +0200, Peter Eisentraut wrote:
> Patrick Welche writes:
> 
> > > I have no objection to the gettext API, but I was and still am concerned
> > > about depending on GNU gettext's code, because of license conflicts.
> > > There is a BSD-license gettext clone project, but it doesn't look to be
> > > very far along.
> >
> > What's missing with it?
> 
> * portability
> 
> At first glance, uses strlcat and strlcpy.  Didn't look further.

As I said, I didn't change anything within the GNU make source to get it to
work. grep strlcat on GNU make, which you must have in order to build
postgresql, returns nothing, however grep gettext does. I chose gmake as an
example which is probably written with portability in mind.

> * dedication to portability
> 
> Only plans to support *BSD.

What does this imply?

HISTORY    The functions are implemented by Citrus project, based on the documenta-    tions for GNU gettext.

> * source code availability
> 
> Didn't find anything outside NetBSD CVS and the CVS rep where they got it
> from.

From libintl.h

/*-* Copyright (c) 2000 Citrus Project,* All rights reserved.** Redistribution and use in source and binary forms, with
orwithout* modification, are permitted provided that the following conditions* are met:* 1. Redistributions of source
codemust retain the above copyright*    notice, this list of conditions and the following disclaimer.* 2.
Redistributionsin binary form must reproduce the above copyright*    notice, this list of conditions and the following
disclaimerin the*    documentation and/or other materials provided with the distribution.** THIS SOFTWARE IS PROVIDED
BYTHE AUTHOR AND CONTRIBUTORS ``AS IS'' AND* ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE*
IMPLIEDWARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE* ARE DISCLAIMED.  IN NO EVENT SHALL THE
AUTHOROR 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
NEGLIGENCEOR OTHERWISE) ARISING IN ANY WAY* OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF*
SUCHDAMAGE.*/
 

which I think counts as a postgresql compatible license? Is that what you
meant?

> * documentation
> 
> Related to above.

The HISTORY bit was quoted from the gettext man page.. What more
documentation is required? AFAIK it's meant to be a direct replacement..

> * English support forum
> 
> Only Japanese mailing list available.

Yes, I wondered about that to.. Luckily PostgreSQL is international!

Cheers,

Patrick


pgsql-hackers by date:

Previous
From: Ian Lance Taylor
Date:
Subject: Re: Re: bug in pgcrypto 0.3
Next
From: Thomas Swan
Date:
Subject: Re: 7.2 items