"Advanced WPKG" (WAS: Re: [wpkg-users] MD5 hash)

[Jerry Haltom]

Take that back, you could resume where you left off. Just not as smartly
as rsync.

On Wed, 2006-04-05 at 10:31 -0500, Jerry Haltom wrote:
> Hmm. I sure thought it did. Doesn't look like it though.
> 
> I might question the actual necessity of distributing software over HTTP
> though, because you wouldn't get the cool benefits of resuming where you
> left off, and software is generally big. Also, you can only do one file
> at a time, not recurse an entire directory, which would defiantly make
> it useless for a whole lot of installs. And if you've got even a single
> installs it doesn't work for, you're not going to be able to use it.
> 
> On Wed, 2006-04-05 at 16:37 +0200, Tomasz Chmielewski wrote:
> > Jerry Haltom wrote:
> > > I actually considered this a long time ago. Simple solution is to bundle
> > > rsync with wpkg and allow one to specify a remote rsync location to
> > > retrieve packages. When this attribute exists, wpkg simply syncs a local
> > > temp directory with the specified one (perhaps resuming where it left
> > > off), and when complete, issues the install command.
> > > 
> > > That rsync location can be either a single file off http, which rsync
> > > already supports, or an rsync server hosting many software installs...
> > > or even a smb path, which rsync would just copy from. Wpkg doesn't have
> > > to implement anything protocol specific at all.
> > 
> > 
> > Does rsync really support http?
> > 
> > I see no reference in rsync documentation that it does (as of version 
> > 2.6.7, which is also the newest).
> > 
> > 
> 
> 
> 

wpkg-users mailing list
wpkg-users at lists.wpkg.org
http://lists.wpkg.org/mailman/listinfo/wpkg-users