Mailinglist Archive: opensuse (2831 mails)

< Previous Next >
Re: [opensuse] New drpmsync Version available
  • From: Michael Schroeder <mls@xxxxxxx>
  • Date: Mon, 10 Jul 2006 18:06:15 +0200
  • Message-id: <20060710160614.GA14393@xxxxxxx>
On Mon, Jul 10, 2006 at 05:19:12PM +0200, Robert Schiele wrote:
> > > Again: My proposal should not influence the way the drpmsync server operates
> > > at all. I intends to provide an _alternative_ way of doing things without
> > > doing any harm (but using about 3MB of disk space) to any other service.
> >
> > Agreed, it wouldn't break things. I'm just a bit reluctant because
> > of the outdated filelist problems, as already stated.
> Well, if it finally proves that my idea was completely crap then we could
> easily remove this file again. But not even trying it just because there
> _might_ be a problem does not really make sense if the is no big risk
> involved.

Ok, I give up. Lets give it a try.

> > > I would even provide a patch for the repository building scripts to do so but
> > > because they are prorietary (Yes, they are!) I cannot do this.
> >
> > What do you mean? The repository is synced with drpmsync (and so
> > the delta rpms are created). There is no secret script.
> > The way to create the on disk filelist would just be another
> > drpmsync call.
> Well, ok, maybe this is the source of some misunderstanding: My idea was to
> create this file immediately when creating the repository (on the same system
> that creates files like INDEX.gz or ARCHIVES.gz). In that case the file will
> be always in sync with the repository at any time a mirror sync is complete.
> Sure the file _could_ be also generated by the drpmsync server but I would
> recommend to decouple this completely (besides the fact that code might be
> shared and that the actual client makes use of the deltas generated by the
> real drpmsync server) because this file describes only states of the files
> contained in the repository. The logic how to use this information to apply
> patches is completely up to the client implementation.

Maybe, but it IMHO makes no sense to put drpmsync code into the
repository creation code. I'll just call drpmsync for the job.


Michael Schroeder mls@xxxxxxx

To unsubscribe, e-mail: opensuse-unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-help@xxxxxxxxxxxx

< Previous Next >
Follow Ups