Mailinglist Archive: zypp-devel (75 mails)
| < Previous | Next > |
Re: [zypp-devel] zypper performance gone bad, bad, bad
- From: Michael Matz <matz@xxxxxxx>
- Date: Tue, 20 May 2008 15:10:19 +0200 (CEST)
- Message-id: <Pine.LNX.4.64.0805201506480.20583@xxxxxxxxxxxxx>
Hi,
On Tue, 20 May 2008, Jan Kupec wrote:
Why not? :-) It doesn't clutter up the sources too much and is not in a
performance sensitive area, so we can do that. OTOH you are right that it
existed only very shortly, but as you can see in this thread even that was
enough that someone was hit by the problem.
I'm not sure this would work. The attributes are extensible, hence
libzypp can't know which attributes are unknown, and which aren't.
Ciao,
Michael.
--
To unsubscribe, e-mail: zypp-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: zypp-devel+help@xxxxxxxxxxxx
On Tue, 20 May 2008, Jan Kupec wrote:
Josef: it would be worthwhile I think to still recognize and parse the
old names (without exposing them in the API) to avoid this problem
with lock files written in the intermediate form.
Why?
Why not? :-) It doesn't clutter up the sources too much and is not in a
performance sensitive area, so we can do that. OTOH you are right that it
existed only very shortly, but as you can see in this thread even that was
enough that someone was hit by the problem.
The old names existed only during two betas or so. Why not just get rid
of them and not pollute the code? Instead a mechanism to detect and log
(at least) an unknown attribute (whether it is a sat attribute or
PoolQuery's own) should be added.
I'm not sure this would work. The attributes are extensible, hence
libzypp can't know which attributes are unknown, and which aren't.
Ciao,
Michael.
--
To unsubscribe, e-mail: zypp-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: zypp-devel+help@xxxxxxxxxxxx
| < Previous | Next > |