Cygdaemon - planning

[Elfyn McBratney]

On Wed, 25 Jun 2003, Christopher Faylor wrote:

> On Wed, Jun 25, 2003 at 05:53:50PM +0100, Elfyn McBratney wrote:
> >I have also changed things quite a lot. I've moved specific daemon code into a
> >new toplevel `cygdaemon' directory and kept/renamed the interface code in the
> >`cygwin' directory. Here's how things look locally on my branch
> >
> >  winsup/
> >    ...
> >    cygdaemon/
> >      ipc-utils/  - a few command line utilities (still a work in progress)
> >      ...
> >    cygwin/
> >      moved cygserver_shm.cc to cygdaemon/modules/shm.cc
> >      ...
> >
> >If it's OK, could I start a branch for developement? After I've finished my work
> >on libgen and submitted the dang patch, of course. :-)
>
> What is the rationale for putting things in a winsup directory?  Can't cygdaemon
> be in it's own sibling directory with winsup?
>
> cgf

Convenience mainly. When I'm rebuilding the daemon after a `make clean' I don't
want to have to rebuild the whole of winsup/cygwin just to see if my one-line
change worked. :-) It's easier for me to manage but if you don't want to move
it, that's cool.

Elfyn
--