This is the mail archive of the cygwin-developers@cygwin.com mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Cygdaemon - planning


On Thu, Jul 03, 2003 at 10:43:16AM -0400, Earnie Boyd wrote:
>Christopher Faylor wrote:
>>On Thu, Jul 03, 2003 at 10:09:57AM -0400, Earnie Boyd wrote:
>>>Christopher Faylor wrote:
>>>>On Thu, Jul 03, 2003 at 11:17:54AM +0200, Corinna Vinschen wrote:
>>>>>Do we want this?  Wouldn't it be better to have a separate export
>>>>>library for the functions only available with cygserver?
>>>>
>>>>
>>>>In this scenario, we have always gone with "what does UNIX do?" I think
>>>>it is pretty likely that the main users of this code will be existing
>>>>programs which expect not to have to look in other libraries to find
>>>>Sys V shm and semaphores.  So, putting the exports in some other
>>>>library will result in configury changes for existing programs which is
>>>>something that cygwin tries to avoid.
>>>
>>>So, there needs to be a method to detect the presence of cygserver
>>>executing or not from the cygwin dll and set an error of ENOSYS if not?
>>
>>Right.  That's what would happen.
>
>So, if the package configury sets HAVE_FUNCTION_FOO when the system
>says ENOSYS the package configury is broken and needs fixed anyway.

I think Corinna was concerned about packages which would, unknowingly,
introduce a dependency on cygserver when there were workarounds available
in the package for cases where cygserver functionality is not present.

cgf


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]