Tue, 9 Jul 2002 22:01:26 +0200 >At 13:57 Uhr +0200 09.07.2002, Stefan Berreth wrote:
[...] >> >>but: can anybody explain to me why the rsync version installed by fink is >>not the HFS+ filesystem enhanced version of rsync? (see <http:// >>www.macosxlabs.org/rsyncx/rsyncx.html>) >> > >[...] > >>- is there a good reason why fink does not install the HFS+ enhanced >>evrsion of a tool when available? > >Because this is the rsync package. Nothing prevents you from making a >"rsyncx" package, though, if it is a command line app. If it is a Mac >OS X GUI app (Cocoa/Carbon), it shouldn't be package via Fink. hmm, the actual commandline tool is the 'original' rsync with added support for HFS+ if both sides have a HFS+ supporting rsync version. So it may well be the default version on OSX. I actually don't understand why apple ships with the non-HFS+ suporting version. And yes, you are right, there is OS X GUI app shipping with the rsyncX archive at the URL above that operates on top of the rsync commandline tool. The GUI app should of course not be part of a fink tool installation. > >In any case the original rsync package will stay, too, for people who >have to use the original version for various reasons. > Whereas i oftern understand the need for this position, I fail to see it in this particular case. The rsync version with HFS+ support is the _identical_ code for non-HFS+ situations. The original package is simply inapropriate for the underlying filesystem on OSX. I don't see why one would prefer using a rsync version that has the identical codepath of the HFS+ supporting version but breaks data when it comes across HFS+ specific file features. We can of course wait until HFS+ support has penetrated the official rsync code trunk and will be available from there. But I'd like to see a more pragmatic and reasonable approach until then. I've cc:ed this mail to bbum, the maintainer of the fink rsync package. I assume he'd have to take the decision wether to move to the HFS+ supporting version of rsync for the fink distributio or not. >>- case this is just because noone has put it into fink yet (or was aware >>of the need), what is the protocol to get it into fink? > >It's all documented on the Fink web page. See: > >http://fink.sourceforge.net/help/index.php >which leads to >http://fink.sourceforge.net/doc/packaging/index.php >http://sourceforge.net/tracker/?atid=414256&group_id=17203 Thanks for the pointers :) - Stefan -- s t e f a n . b e r r e t h - [EMAIL PROTECTED] pgp key fingerprint: AB14 A3F2 E163 ADA2 6444 9AC6 2942 518E 3F78 4FAF pgp = pretty good privacy, see http://www.pgpi.org/ ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Two, two, TWO treats in one. http://thinkgeek.com/sf _______________________________________________ Fink-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-users
