resurrecting this thread a bit late, but... On Thu, Dec 01, 2005 at 07:08:43PM +0100, Marius Mauch wrote: > emerge-webrsync is such a thing I'd rather > keep inline (should be subject for integration into emerge --sync > instead),
Agreed, _long term_. Short term, till an actual sync refactoring is available, improvements I've pegged into emerge-delta-webrsync I'd like to move into emerge-webrsync. The main one is tarsync. Normal webrsync works by untarring to a tmp, then rsync'ing that onto $PORTDIR; hence tarsyncs existance, it bypasses the innefficient intermediate dumping of files, and does updates directly from the tarball to the tree. Sounds like something tar could do, but unfortunately tar lacks any syncing on disk dirs to match *exactly* the tarball- iow, files get left behind. Tarsync supports RSCYNC_EXLUDE syntax already, and for it's 4-6 month existance hasn't yet had a single bug via emerge-delta-webrsync testing- granted, not a huge userbase, but I'd peg it in the hundreds. So... thoughts? I'm not much for making portage depend on tarsync just for emerge-webrsync improvements, would rather chunk the bugger out. ~harring
pgpS7npTU34l8.pgp
Description: PGP signature
