Mailinglist Archive: zypp-devel (52 mails)
| < Previous | Next > |
Re: [zypp-devel] Re: next-gen API for package management?
- From: Klaus Kaempf <kkaempf@xxxxxxx>
- Date: Tue, 20 Sep 2011 15:04:47 +0200
- Message-id: <20110920130447.GA5101@heron.suse.de>
* Klaus Kaempf <kkaempf@xxxxxxx> [Sep 20. 2011 14:28]:
Oh, I forgot to mention one important property of the xsolvable
approach. It gives you the flexibility to create solvables and add
them to the pool during runtime.
IIRC we dicussed creating patches in libzypp at runtime and the
libzypp approach (resulting in a static pool) prevented that.
Klaus
---
SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB
16746 (AG Nürnberg)
Maxfeldstraße 5, 90409 Nürnberg, Germany
--
To unsubscribe, e-mail: zypp-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: zypp-devel+help@xxxxxxxxxxxx
* Duncan Mac-Vicar P. <dmacvicar@xxxxxxx> [Sep 20. 2011 14:19]:
I am quite surprised that you find this a bug, when you had to do
exactly the same once and invent xsolvable. ZYpp just took a
different path and prefered to manage one pool instead of adding one
Pool pointer to each solvable.
Oh, I forgot to mention one important property of the xsolvable
approach. It gives you the flexibility to create solvables and add
them to the pool during runtime.
IIRC we dicussed creating patches in libzypp at runtime and the
libzypp approach (resulting in a static pool) prevented that.
Klaus
---
SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB
16746 (AG Nürnberg)
Maxfeldstraße 5, 90409 Nürnberg, Germany
--
To unsubscribe, e-mail: zypp-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: zypp-devel+help@xxxxxxxxxxxx
| < Previous | Next > |