Re: [P4W-posixdev] Hmm.... 10 downlaods of p4wposix

[Ronald Landheer-C. <ro...@la...>]

Okay.. I think you're cutting a bit too many corners here..
I really don't think it's a good idea to release a DLL that has all the 
markings of Cygwin still on it (API version, original name, product name, 
internal name, organisation, registry key - the bunch)

I don't want to blow down on your enthusiasm, but as long as there is no 
actual development, there shouldn't be any releases either.

I also think we should take a look at what we really want to do - do we 
want a full-blown fork of Cygwin with an external runtime library, an 
external file system manager, etc. etc. or do we want to start off just 
trying to get two versions of Cygwin living together peacefully, and 
*then* adjusting Cygwin to our wishes?

Personally, I think most of the ideas I have seen so far are good ones, 
but I think we should take it one step at a time, so as not to lose track 
of the project before it's even started.

I propose the following steps (and note they are, IMHO, already quite big)
1. Get p4w-posix to live together peacefull with Cygwin and MSYS
   make it so that MSYS programs can launch p4w-posix programs, cygwin 
   programs can launch p4w-posix programs and p4w-posix programs can 
   launch MSYS/Cygwin programs
   (Changes to this effect may be interesting for MSYS, even if cgf is 
   not interested in them for Cygwin)
2. Make as many features as possible optional at configure-time
   e.g. --with-symlinks --without-sockets
3. Separate the POSIX emulation layer from the C library
   i.e. make a separate runtime library. This is where newlib.dll and/or 
   glibc.dll become a great idea
   This is also where it might become possible to no longer need Newlib 
   for the POSIX emulation at all - we might be able to use msvcrt
4. Make more modules ...
   ... such as the file system emulation

IMHO, all if this should be done sticking as closely to the Cygwin 
code-base as possible - there is a lot of active use and development on 
the Cygwin project, and it is open source, so we might as well use it.
This basically means we're developing a set of patches to the Cygwin 
code-base, and maintaining those patches relative to Cygwin. This means 
the CVS repository containing p4w-posix should be kept in sync with Cygwin 
- at least with the releases (I don't think it's feasible to keep in sync 
with Cygwin CVS)

Let me know what you think :)

rlc

On Tue, 25 Feb 2003, Earnie Boyd wrote:

> Ok, so what does the list of 3 members think so far?
> 
> Earnie.
> 
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> P4W-posixdev mailing list
> P4W...@li...
> https://lists.sourceforge.net/lists/listinfo/p4w-posixdev
>