in reply to Directory Syncer

Sorry for being a party pooper :-), but — does this do anything rsync doesn't already do better?

Makeshifts last the longest.

Replies are listed 'Best First'.
Re^2: Directory Syncer
by Mr_Person (Hermit) on Aug 18, 2004 at 14:27 UTC
    If you ever want to synchronize in both directions, Unison works really well and has a few other features that rsync doesn't.
Re^2: Directory Syncer
by jkva (Chaplain) on Aug 18, 2004 at 12:20 UTC
    Yep... but until 2 hours ago rsync was yet unknown to me :)
    Thanks for the tip though.

    Detonite
Re^2: Directory Syncer
by graff (Chancellor) on Aug 19, 2004 at 07:28 UTC
    does this do anything rsync doesn't already do better?

    Hmm. Does rsync provide status/error messages in Dutch?

      No, it doesn't. It isn't even gettextized, unfortunately.

      Retrofitting gettext support and writing a Dutch translation would be a worthy way to invest one's effort if that is an important criteria. :-)

      Makeshifts last the longest.

Re^2: Directory Syncer
by jbware (Chaplain) on Aug 18, 2004 at 16:14 UTC
    To throw another solution on the fire, robocopy works wonders on the Windows platform.

    Existing solutions aside, kudos on the learning initative. I've reinvented many a wheel myself for the sake of learning :)

    -jbWare

      Of course, as I have said many times and will say again: there's nothing wrong with reinventing wheels for the sake of learning, but a lot with subsequently using them in production unless you actually intend to spend the time and effort to invent a rounder wheel than what's already there. That means knowing how existing wheels solve the problem, understanding what issues they have, getting your code out to as many people as possible for testing, and sticking around fixing bugs as they come up. Only then can you be confident that your code is correct and robust enough to withstand abuse from many different users with lots of different needs and scenarios.

      Of course, it is quite enlightening to invent your own wheel, then read an existing one for comparison. There'll be checks and code for all these strange conditions and edge cases you never even thought of. I learned a number of valuable lessons that way.

      And if you do that three or four times, you'll cease trying to invent your own wheels in the first place and start giving advice such as what I have ended up giving. :-)

      Makeshifts last the longest.

        Valuable reasons for re-inventing wheels:
        • You apreciate what others have done before, and what is polishing the results. (4 x. doing it user friendly, or error proof).
        • You find yourself that 'you are not the only one' :) And you could measure the public success that your idea could have become if you had done it some time before.
        • By comparing the code (thanks to opensource), you can improve your syntax and the way of procesing the data.
        • Finally, you can clasify your chunks of code and re-use them in other projects. You need to improve your self-documenting style, in order to reuse it with just a glimpse at it and not having to inspect it in detail. Also, re-structuring it in clear chunks would help a lot!

        .{\('v')/}
        _`(___)' __________________________