X-Git-Url: https://mattmccutchen.net/rsync/rsync.git/blobdiff_plain/46ef7d1dc8e8f25ef2e2f9d13272c8edb77545b6..053f3a831defdbd30f15e58fd0cb23b3f71c5af7:/TODO diff --git a/TODO b/TODO index dd044859..29dd10f5 100644 --- a/TODO +++ b/TODO @@ -2,20 +2,99 @@ URGENT --------------------------------------------------------------- + +IMPORTANT ------------------------------------------------------------ + +Cross-test versions + + Part of the regression suite should be making sure that we don't + break backwards compatibility: old clients vs new servers and so + on. Ideally we would test the cross product of versions. + + It might be sufficient to test downloads from well-known public + rsync servers running different versions of rsync. This will give + some testing and also be the most common case for having different + versions and not being able to upgrade. + +use chroot + + If the platform doesn't support it, then don't even try. + + If running as non-root, then don't fail, just give a warning. + (There was a thread about this a while ago?) + + http://lists.samba.org/pipermail/rsync/2001-August/thread.html + http://lists.samba.org/pipermail/rsync/2001-September/thread.html + +--files-from + + Avoids traversal. Better option than a pile of --include statements + for people who want to generate the file list using a find(1) + command or a script. + +Performance + + Traverse just one directory at a time. Tridge says it's possible. + + Can possibly also be smarter about memory use while looking for hard + links by reducing the refcount as we find alternative names. + +IPv6 + + Define a syntax for IPv6 literal addresses. Since they include + colons, they tend to break most naming systems, including ours. + Based on the HTTP IPv6 syntax, I think we should use + + rsync://[::1]/foo/bar + [::1]::bar + + which should just take a small change to the parser code. + +PLATFORMS ------------------------------------------------------------ + +Win32 + + Don't detach, because this messes up --srvany. + + http://sources.redhat.com/ml/cygwin/2001-08/msg00234.html + + According to "Effective TCP/IP Programming" (??) close() on a socket + has incorrect behaviour on Windows -- it sends a RST packet to the + other side, which gives a "connection reset by peer" error. On that + platform we should probably do shutdown() instead. However, on Unix + we are correct to call close(), because shutdown() discards + untransmitted data. + +BUILD FARM ----------------------------------------------------------- + +Add machines + + AMDAHL UTS (Dave Dykstra) + + Cygwin (on different versions of Win32?) + + HP-UX variants (via HP?) + NICE ----------------------------------------------------------------- -Merge IPv6 support *** +--no-detach and --no-fork options + + Very useful for debugging. Also good when running under a + daemon-monitoring process that tries to restart the service when the + parent exits. + +hang/timeout friendliness + + On -A patch is available at +internationalization - ftp://ftp.kame.net/pub/kame/misc/rsync-244-v6-20000802.diff.gz + Change to using gettext(). Probably need to ship this for platforms + that don't have it. -but tridge reckons it needs to be cleaned up before it can be -accepted. + Solicit translations. -This is now on the track-kameipv6 branch and can be moved across any -time. The KAME people say that it should work on machines without -IPv6 stacks. + Does anyone care? rsyncsh