[Xastir-dev] Cygwin port detect/new stable release

[Jack Twilley]

WARNING: Unsanitized content follows.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

>>>>> "Curt" == Curt Mills <archer at eskimo.com> writes:

Curt> The answers I got on the Cygwin mailing list point to the fact
Curt> that com1 and /dev/ttyS0 are handled exactly the same in the
Curt> code, and there is no Windows-version-specific code in that
Curt> section.

Curt> That means to me that if we do a detect using "test -c
Curt> /dev/ttyS0" we'll run into the same sort of hang on some WinXP
Curt> boxes as we did with "test -c com1".

Better safe than sorry, but I'm looking forward to that fix.  Did the
mailing list have any reports of problems like this?

Curt> For that reason I'm going to suggest we stick with the "test -d
Curt> /dev/registry", even though I don't like that, and put out a new
Curt> stable release right away.

Okay.  I think you had /proc/registry, but I can't remember.

Curt> The stable release will have that device-detect hang fixed and
Curt> will have the correct URL for terraserver/toposerver in it.

Curt> If anyone has any objections, please voice them immediately.
Curt> I'll plan to do a new stable release (1.3.1) later today or
Curt> early tomorrow.

One thing that's annoyed me -- can the maps currently in the top-level
be put in a directory (named something like "server" or "online") so
that they can be manipulated with the chooser?

Jack.
- -- 
Jack Twilley
jmt at twilley dot org
http colon slash slash www dot twilley dot org slash tilde jmt slash
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (FreeBSD)

iD8DBQFAYyDzGPFSfAB/ezgRAtz8AJ9IwlirIspjSCr/VTng6jTFc6qrrwCeJ9x1
tnq/2kcPlAHwynl+aFJq61M=
=ow0u
-----END PGP SIGNATURE-----