Re: PG+Cygwin Production Experience (was RE: Path to PostgreSQL

Поиск
Список
Период
Сортировка
От Barry Lind
Тема Re: PG+Cygwin Production Experience (was RE: Path to PostgreSQL
Дата
Msg-id 3CDAA21F.7020300@xythos.com
обсуждение исходный текст
Ответ на Re: PG+Cygwin Production Experience (was RE: Path to PostgreSQL porta biliy)  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-hackers

Tom Lane wrote:
> "Henshall, Stuart - WCP" <SHenshall@westcountrypublications.co.uk> writes:
> 
>>Cygwin is not the only additon needed, cygipc will also be needed (GPL)
>>(see: http://www.neuro.gatech.edu/users/cwilson/cygutils/cygipc/index.html )
> 
> 
> Good point, but is this a requirement that we could get rid of, now that
> we have the SysV IPC stuff somewhat isolated?  AFAICT cygipc provides
> the SysV IPC API (shmget, semget, etc) --- but if there are usable
> equivalents in the basic Cygwin environment, we could probably use them
> now.
> 
> Considering how often we see the forgot-to-start-cygipc mistake,
> removing this requirement would be a clear win.
> 
>             regards, tom lane

There is some work going on within cygwin to make the separate cygipc 
stuff less of a problem.  They are trying to integrate SysV IPC 
functionality it into the core cygwin.dll.  However because of licensing 
issues (the current cygipc code is GPL and RedHat currently as the 
copyright holder on the core cygwin code releases it for a fee under 
other licenses in addition to the GPL) there are some problems with 
doing that.

thanks,
--Barry




> 
> ---------------------------(end of broadcast)---------------------------
> TIP 3: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo@postgresql.org so that your
> message can get through to the mailing list cleanly
> 




В списке pgsql-hackers по дате отправления:

Предыдущее
От: Thomas Lockhart
Дата:
Сообщение: Re: pgaccess
Следующее
От: Barry Lind
Дата:
Сообщение: Re: PG+Cygwin Production Experience (was RE: Path to PostgreSQL