Hi everyone We are using rsync on Windows and despite the efforts by the cygwin and mingw people it would be nice to see win32 support upstream. When trying to port the latest version of rsync to Windows (not finished yet) I started using parts of gnulib [1] for missing headers, definitions and functions. While gnulib can be used without automake by generating the headers, copying and manually adding them it seems to be a lot easier if automake is used for building. Therefore: * Would a patch which changes the build system to automake get accepted? * Would the inclusion of gnulib as git submodule (similar to libvirt's gnulib inclusion) be acceptable? * Would a patch which makes the rsync-daemon optional get accepted? (since this is where win32 differs the most and is therefore the trickiest part to port) Best regards, Tiziano [1] http://www.gnu.org/software/gnulib/ -- stepping stone GmbH Neufeldstrasse 9 CH-3012 Bern Telefon: +41 31 332 53 63 www.stepping-stone.ch tiziano.mueller at stepping-stone.ch
[Sorry for the super-late reply.] On Tue, Sep 24, 2013 at 2:40 AM, Tiziano M?ller < tiziano.mueller at stepping-stone.ch> wrote:> * Would a patch which changes the build system to automake get accepted? >I'd be glad to consider that. * Would the inclusion of gnulib as git submodule (similar to> libvirt's gnulib inclusion) be acceptable? >I'm not very keen on that idea for the main code. * Would a patch which makes the rsync-daemon optional get accepted?>Yes, I believe so. It shouldn't make things too much more complicated, and allows the building of just the copy-tool side. ..wayne.. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.samba.org/pipermail/rsync/attachments/20140101/b790fb48/attachment.html>