Mailinglist Archive: zypp-devel (70 mails)
| < Previous | Next > |
Re: [zypp-devel] my plan: SOLV files for libzypp
- From: Klaus Kaempf <kkaempf@xxxxxxx>
- Date: Mon, 8 Oct 2007 11:50:52 +0200
- Message-id: <20071008095052.GB16547@xxxxxxxxxxxxx>
* Michael Matz <matz@xxxxxxx> [Oct 08. 2007 11:40]:
> Aloha,
>
> for your viewing pleasure here are my weekend hacks (and this time it's
> really really horrible, don't look at them) to make libzypp use SOLV files
> instead of sqlite and rpm database as backends.
Hey, thanks a lot and welcome to the zypp coders team ! :-)
>
> And it duplicates code. And it doesn't do error checking. And it kill
> kittens, when someone reads it.
Too bad you included the patch in the mail to zypp-devel where we have
approx. 20 subscribers and hence 20 dead kittens now.
[...]
>
> I'm personally planning to do more about this. In particular working with
> mls on extending the .solv format a bit to store also some other
> information about resolvables.
Participation and help is very welcome and you're invited to share
your plans with us so we can plan and organize future work.
>
> I haven't yet made up my mind if the SQLite database will stay or not.
> It's quite nice to have for some information (as it's easily extensible),
> but the necessity to then maintain a mapping from resolvable-ID (in
> zypp.db) to source/resolvable-id (in SOLV) makes this less attractive.
The current thinking on this topic is to keep the database for
on-demand retrieval of UI information (summary, description, license,
...) and for extended search.
>
> Anyway, so you know about my plans, here's my current
> patch^Whack^Wunbelievable bloody crap.
>
Does it compile ? Does it run ? Lets ship it ! ;-)
Klaus
---
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
--
To unsubscribe, e-mail: zypp-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: zypp-devel+help@xxxxxxxxxxxx
> Aloha,
>
> for your viewing pleasure here are my weekend hacks (and this time it's
> really really horrible, don't look at them) to make libzypp use SOLV files
> instead of sqlite and rpm database as backends.
Hey, thanks a lot and welcome to the zypp coders team ! :-)
>
> And it duplicates code. And it doesn't do error checking. And it kill
> kittens, when someone reads it.
Too bad you included the patch in the mail to zypp-devel where we have
approx. 20 subscribers and hence 20 dead kittens now.
[...]
>
> I'm personally planning to do more about this. In particular working with
> mls on extending the .solv format a bit to store also some other
> information about resolvables.
Participation and help is very welcome and you're invited to share
your plans with us so we can plan and organize future work.
>
> I haven't yet made up my mind if the SQLite database will stay or not.
> It's quite nice to have for some information (as it's easily extensible),
> but the necessity to then maintain a mapping from resolvable-ID (in
> zypp.db) to source/resolvable-id (in SOLV) makes this less attractive.
The current thinking on this topic is to keep the database for
on-demand retrieval of UI information (summary, description, license,
...) and for extended search.
>
> Anyway, so you know about my plans, here's my current
> patch^Whack^Wunbelievable bloody crap.
>
Does it compile ? Does it run ? Lets ship it ! ;-)
Klaus
---
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
--
To unsubscribe, e-mail: zypp-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: zypp-devel+help@xxxxxxxxxxxx
| < Previous | Next > |