From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Table Spaces |
Date: | 2004-05-19 15:17:33 |
Message-ID: | 40AB7A8D.4070006@dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
pgsql(at)mohawksoft(dot)com wrote:
>>On Wednesday 19 May 2004 00:19, pgsql(at)mohawksoft(dot)com wrote:
>>
>>
>>>>pgsql(at)mohawksoft(dot)com wrote:
>>>>
>>>>
>>>>>This makes me worried. That's the way we *used* to do things, but the
>>>>>sleazy IP lawyers are looking for anything with which they can create
>>>>>the
>>>>>impression of impropriety. The open source and free projects are
>>>>>
>>>>>
>>>ground
>>>
>>>
>>>>>zero for this crap.
>>>>>
>>>>>We *really* need to be careful.
>>>>>
>>>>>
>>>>I assumed this tool was GPL and we just needed to avoid the GPL issue.
>>>>
>>>>
>>>I'm probably just being alarmist, but think about some IP lawyer buying
>>>up
>>>the entity that owns the GPL code, and suing end user's of PostgreSQL.
>>>
>>>This is similar to what is happening in Linux land with SCO.
>>>
>>>The best defense is to say, nope, we didn't copy your stuff, we
>>>implemented it ourselves based on the documentation.
>>>
>>>
The safe bet if we want to use junction points is to use clean room
techniques. I understand from other comments that it wouldn't be difficult.
cheers
andrew
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2004-05-19 15:26:11 | Re: Rough draft for Unicode-aware UPPER()/LOWER()/INITCAP() |
Previous Message | Tom Lane | 2004-05-19 14:58:47 | Re: proposal: be smarter about i/o patterns in index scan |