> Magnus Hagander wrote:
>> >>If you run NTFS, it's still possible to use arbitrary links.
>> >In the Windows
>> >>world, they are called junctions. Microsoft does not provide
>> >a junction tool
>> >>for some reason (perhaps because it's limited to NTFS). A
>> >good tool, free
>> >>and with source, can be found here
>> >>http://www.sysinternals.com/ntw2k/source/misc.shtml#junction
>> >I use this tool
>> >>myself. Works like a charm.
>> >>
>> >>
>> >>
>> >
>> >We've looked at it before. Apart from anything else I don't think its
>> >license is compatible with PostgreSQL's.
>>
>> Well, people can still use it. We just can't distribute it... We can
>> always link to it.
>> But unless there is a GUI tool (actually, unless it shows up in the
>> *default* GUI tool), expect there to be questions. An
>
> I assume we can just look at the source and write our own version
> bypassing any license.
I wouldn't be so sure about that. If this insane SCO crap has taught me
anything, the PostgreSQL should have a defined and legally vetted process
for duplicating functionality. ala' phoenix BIOS.
What would be good is a "contaminated" developer specifying functionality,
and detailing the various APIs needed (documenting the undocumented ones
as nessisary) while someone else writes the code. It is the *only* legal
unemcumbered methodology that will work.
