Without this you may get
print('Removing file %s (backup in )' % (path, backup))
^~~~
TypeError: not all arguments converted during string formatting
./bootstrap: gnulib-tool failed
~mitch (they, them)
pygnulib_minor_bug.patch
Description: Bi
I am doing some quick and dirty things currently for compiling a slew of
(mostly) gnu software of Windows. I hope to have some semi-quality
patches to submit soon enough.
I have been very grateful for gnulib-tool.py as it results in some massive
bootstrap speed improvements (over 10x) on Windows
> It's nice that you consider enhancing gnulib-tool.py. But don't
underestimate
the task:
Yes, this suggestion was _only_ to support situations where no
automake-subdir was required and we stripped the path.I have automated
several build packages so could likely automate testing of the
gnulib-
Thanks Bruno for such detailed notes. I will start to work on cleaning up
the patches to prep for the mailing list.
> When a package has complicated fork/exec logic, generally it's advisable
to
> use the posix_spawn facility when possible. This provides not only
portability
> to native Windows; i
> If I have understood it correctly, the best way to handle file names on
native
> Windows is to
> - use '\\' as a directory separator when composing file names,
> - allow both '/' and '\\' when inspecting file names.
Yes, that is largely what I implemented. There is a platform
specific DIR_SEPA
> The current state is an attempt to make code compile if it doesn't use
> or . I don't know whether this state can be significantly
> improved. But if you have reasonable suggestions, please show them!
For requests to get the actual username I don't know if it is better to:
1) Try the official A
