Hi Dan, Can you explain what is the relationship (if any) between /usr/bin/rsync and librsync ?
Would it be possible to build /usr/bin/rsync by linking to this library as seems sensible? Trev Daniel Hain wrote: > I'm submitting this fast-track for Pradhap Devarajan. The timer is set for > April 15th, 2008. > > Dan > > > Template Version: @(#)onepager.txt 1.35 07/11/07 SMI > Copyright 2007 Sun Microsystems > > 1. Introduction > 1.1. Project/Component Working Name: > > Integrate librsync library into Solaris > > 1.2. Name of Document Author/Supplier: > > Pradhap Devarajan > > 1.3. Date of This Document: > 03/20/2008 > > 1.4. Name of Major Document Customer(s)/Consumer(s): > 1.4.1. The PAC or CPT you expect to review your project: > Solaris PAC > 1.4.2. The ARC(s) you expect to review your project: > PSARC > 1.4.3. The Director/VP who is "Sponsoring" this project: > Chris.Armes at sun.com > 1.4.4. The name of your business unit: > Solaris Revenue Product Engineering > > 1.5. Email Aliases: > 1.5.1. Responsible Manager: joe.g at sun.com > 1.5.2. Responsible Engineer: pradhap.devarajan at sun.com > 1.5.4. Interest List: > > 2. Project Summary > 2.1. Project Description: > > librsync is a free software library that implements the rsync > remote-delta algorithm. > > > 4. Technical Description: > > Summary: > This project integrates librsync-0.9.7 into Solaris > This project requests a micro binding. > > 4.1. Details: > librsync is a free software library that implements the > rsync remote-delta algorithm. > This algorithm allows efficient remote updates of a file, without > requiring the old > and new versions to both be present at the sending end. The > library uses a "streaming" > design similar to that of zlib with the aim of allowing it to be > embedded into many > different applications. > > librsync has been developed by Martin Pool <mbp at samba.org> with > Andrew Tridgell <tridge at samba.org> > > 4.5. Interfaces: > > Standard C Library Functions > Socket Library Functions > > 4.6. Doc Impact: > > New man page: rdiff.1 librsync.3 (see case directory) > > 4.11. Security Impact: > None. > > 4.12 Deliverables: > > SPARC:- > ------- > usr/bin/rdiff > usr/include/librsync.h > usr/include/librsync-config.h > usr/lib/librsync.so > usr/lib/librsync.so.1 > usr/lib/librsync.so.1.0.2 > usr/bin/sparcv9/rdiff > usr/lib/sparcv9/librsync.so > usr/lib/sparcv9/librsync.so.1 > usr/lib/sparcv9/librsync.so.1.0.2 > i386:- > ------- > usr/bin/rdiff > usr/include/librsync.h > usr/include/librsync-config.h > usr/lib/librsync.so > usr/lib/librsync.so.1 > usr/lib/librsync.so.1.0.2 > usr/bin/amd64/rdiff > usr/lib/amd64/librsync.so > usr/lib/amd64/librsync.so.1 > usr/lib/amd64/librsync.so.1.0.2 > > > 5. References: > http://librsync.sourceforge.net/ > > 6. Resources and Schedule: > 6.4. Product Approval Committee requested information: > 6.4.1. Consolidation or Component Name: > sfw > > 6.5. ARC review type: > FastTrack > > 6.6. ARC Exposure: > open > > -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 3253 bytes Desc: S/MIME Cryptographic Signature URL: <http://mail.opensolaris.org/pipermail/opensolaris-arc/attachments/20080409/c8fae626/attachment.bin>
