On Sat, 2008-03-01 at 10:57 +0100, Guido Serassio wrote: 
> This is very critical on the side of the DOS/Unix 
> text format: Visual Studio doesn't work with Unix text files.
> Usually I commit the files on this directory only from Windows machines.

Thats easy to deal with, in fact most likely not really an issue unless
you do a checkout from a different environment than you build..

> > lib/getopt.c. Copy from NetBSD with a license incompatible with GPL.
> 
> Right, someone could provide a GPL version ?

One from either
- FreeBSD
- uclibc
- glibc
- or a number of other projects
should be fine.. but I suspect the glibc one has to much of
dependencies..

BSD / GPL / Public Domain


> > > port/win32/src/encrypt.c. 56 bit DES encryption. Still under export
> > > control in some regoins of the world, but not really a problem. Could be
> > > in lib/ to support other platforms without crypt().
> 
> As I know, it's missing only on Visual Studio.

I can imagine it missing on may other platforms as well.. it's no longer
considered a good pasword hashing method.

> > > port/win32/src/readdir.c. Unknown copyright or license.
> > >
> 
> This is also unknown to me.

Not good. From where did you get it?

> Just discovered another reason to maintain a 
> separate 3.0 STABLE NT branch: currently STABLE 
> 3.0 doesn't work on Windows, so this the only 
> STABLE based branch where to develop and test the needed changes.

Not convinced this is a reason. If you need to make changes for Windows
then it's best if these changes is done in a way which fits all..

And having code, even if Windows specific, in the windows branch is a
very bad thing as it makes it a lot harder for the project to audit the
codebase.

> Regarding to Squid 2, if in the future there is 
> no plan for intrusive changes on the IPC/FD side 
> that could affect the Windows port, a merge into 
> a single branch could be considered.

Who knows. But I don't see the windows port so special in that regard.
We already have differences between many platforms. Sure, Windows is a
little more different, but not very much.

Regards
Henrik

Reply via email to