On Wed, Dec 9, 2020 at 4:50 AM Jonathan Gray <[email protected]> wrote: > > On Tue, Dec 08, 2020 at 11:36:37PM -0700, [email protected] wrote: > > The game battlestar has source files names com1.c through com7.c, which > > are illegal on windows due to ancient dos com port rules. > > > > I understand there might not be much sympathy for that, but being able > > to have the full source tree on a windows system can be convenient, and > > it should be a painless change. > > > > Any chance someone could do that rename in the repository and change > > the Makefile? > > NetBSD renamed them all to command for that reason. > > https://docs.microsoft.com/en-us/windows/win32/fileio/naming-a-file > > usr.sbin/pkg_add/pod/OpenBSD::*.pod would also be a problem due to colons >
Hi John, maybe you can say more how you're getting the files to a windows system? If we rename the battlestar files, and given it won't completely solve things for you as jsg@ points out, does it make any difference for you? I do this myself too from time to time by extracting the src.tar.gz using 7z (https://www.7-zip.org/). That tool seems to automatically rename the comX.c files to _comX.c. And for the pod files it seems to automatically replace the invalid ":" characters with "_". The only annoyance I have left is that there are a small number of remaining conflicts from upper/lower case on unix vs windows. Bottom line, for me extracting with 7z and just pressing "automatically rename" on the first conflict seems to work as all those conflicting filenames are for things I really don't look at on my windows box. But maybe you could tell us more if changing battlestar would partially improve things for you? Either way, I don't object to syncing battlestar with netbsd's 2001 commit.
