Re: [HACKERS] contrib/fuzzystrmatch/dmetaphone.c license

2015-04-30 Thread Bruce Momjian
On Wed, Feb 25, 2015 at 08:36:49PM -0500, Andrew Dunstan wrote: I doubt we want to rip it out without some suitable replacement -- do we? That's more than 10 years ago. I remember creating this for my then work at the North Carolina State Highway Patrol and sending it to Joe, but that's

Re: [HACKERS] contrib/fuzzystrmatch/dmetaphone.c license

2015-02-26 Thread Michael Paquier
On Thu, Feb 26, 2015 at 8:56 AM, Stephen Frost sfr...@snowman.net wrote: * Jim Nasby (jim.na...@bluetreble.com) wrote: On 2/25/15 4:10 PM, Andrew Dunstan wrote: On 02/25/2015 11:59 AM, Joe Conway wrote: It's largely because of such uncertainties that I have been advised in the past (by

Re: [HACKERS] contrib/fuzzystrmatch/dmetaphone.c license

2015-02-25 Thread Heikki Linnakangas
On 02/25/2015 06:59 PM, Joe Conway wrote: I doubt we want to rip it out without some suitable replacement -- do we? No, probably not. I think there are a few options: 0. Find out that the current situation is OK, and the Artistic license is not a problem the way the code is used. 1. Ask

Re: [HACKERS] contrib/fuzzystrmatch/dmetaphone.c license

2015-02-25 Thread Joe Conway
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/24/2015 04:47 AM, Dave Page wrote: On Tue, Feb 24, 2015 at 12:24 PM, Heikki Linnakangas hlinnakan...@vmware.com wrote: contrib/fuzzystrmatch/dmetaphone.c says this: /* COPYRIGHT NOTICES ***

Re: [HACKERS] contrib/fuzzystrmatch/dmetaphone.c license

2015-02-25 Thread Andrew Dunstan
On 02/25/2015 11:59 AM, Joe Conway wrote: It's largely because of such uncertainties that I have been advised in the past (by those with appropriate letters after their names) to stop using the Artistic licence. This is why I spent nearly a year working on changing pgAdmin to the PostgreSQL

Re: [HACKERS] contrib/fuzzystrmatch/dmetaphone.c license

2015-02-25 Thread Stephen Frost
* Jim Nasby (jim.na...@bluetreble.com) wrote: On 2/25/15 4:10 PM, Andrew Dunstan wrote: On 02/25/2015 11:59 AM, Joe Conway wrote: It's largely because of such uncertainties that I have been advised in the past (by those with appropriate letters after their names) to stop using the

Re: [HACKERS] contrib/fuzzystrmatch/dmetaphone.c license

2015-02-25 Thread Jim Nasby
On 2/25/15 4:10 PM, Andrew Dunstan wrote: On 02/25/2015 11:59 AM, Joe Conway wrote: It's largely because of such uncertainties that I have been advised in the past (by those with appropriate letters after their names) to stop using the Artistic licence. This is why I spent nearly a year

Re: [HACKERS] contrib/fuzzystrmatch/dmetaphone.c license

2015-02-25 Thread Andrew Dunstan
On 02/25/2015 06:44 PM, Jim Nasby wrote: On 2/25/15 4:10 PM, Andrew Dunstan wrote: On 02/25/2015 11:59 AM, Joe Conway wrote: It's largely because of such uncertainties that I have been advised in the past (by those with appropriate letters after their names) to stop using the Artistic

Re: [HACKERS] contrib/fuzzystrmatch/dmetaphone.c license

2015-02-24 Thread Dave Page
On Tue, Feb 24, 2015 at 12:24 PM, Heikki Linnakangas hlinnakan...@vmware.com wrote: contrib/fuzzystrmatch/dmetaphone.c says this: /* COPYRIGHT NOTICES *** Most of this code is directly from the Text::DoubleMetaphone perl module version 0.05