Mailinglist Archive: zypp-devel (116 mails)
| < Previous | Next > |
Re: [zypp-devel] Source refresh policy
- From: Michael Andres <ma@xxxxxxx>
- Date: Thu, 21 Jun 2007 12:08:00 +0200
- Message-id: <20070621100800.GA15446@xxxxxxx>
On Wed, Jun 20, Duncan Mac-Vicar wrote:
> > 2. Tools which should install a package. They should work as fast as
> > possible. we can pay the price of installing package which already has an
> > update at least in some cases.
>
> This assumption is false in most cases. If the metadata is old then what will
> happen is that you will solve a old package that will probably match (because
> packages usually doesnt change dependencies often), but the link (filename)
> will be wrong and the package will fail.
>
> This exposes a failure in metadata design, only updating the filenames will be
> a quite option for the use case you mention.
>
> Your usecase works if the repo keeps the old version of the package as well
> (or more).
It works a s well, if commit first downloads all packages.
The bad case is that we find a package being unavailable DURING commit.
If we spot it in advance there is no problem. You just wasted a little
time to solve the old stuff.
--
cu,
Michael Andres
+------------------------------------------------------------------+
Key fingerprint = 2DFA 5D73 18B1 E7EF A862 27AC 3FB8 9E3A 27C6 B0E4
+------------------------------------------------------------------+
Michael Andres YaST Development ma@xxxxxxxxxx
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg)
Maxfeldstrasse 5, D-90409 Nuernberg, Germany, ++49 (0)911 - 740 53-0
+------------------------------------------------------------------+
--
To unsubscribe, e-mail: zypp-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: zypp-devel+help@xxxxxxxxxxxx
> > 2. Tools which should install a package. They should work as fast as
> > possible. we can pay the price of installing package which already has an
> > update at least in some cases.
>
> This assumption is false in most cases. If the metadata is old then what will
> happen is that you will solve a old package that will probably match (because
> packages usually doesnt change dependencies often), but the link (filename)
> will be wrong and the package will fail.
>
> This exposes a failure in metadata design, only updating the filenames will be
> a quite option for the use case you mention.
>
> Your usecase works if the repo keeps the old version of the package as well
> (or more).
It works a s well, if commit first downloads all packages.
The bad case is that we find a package being unavailable DURING commit.
If we spot it in advance there is no problem. You just wasted a little
time to solve the old stuff.
--
cu,
Michael Andres
+------------------------------------------------------------------+
Key fingerprint = 2DFA 5D73 18B1 E7EF A862 27AC 3FB8 9E3A 27C6 B0E4
+------------------------------------------------------------------+
Michael Andres YaST Development ma@xxxxxxxxxx
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg)
Maxfeldstrasse 5, D-90409 Nuernberg, Germany, ++49 (0)911 - 740 53-0
+------------------------------------------------------------------+
--
To unsubscribe, e-mail: zypp-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: zypp-devel+help@xxxxxxxxxxxx
| < Previous | Next > |