[zypp-devel] Packagekit backend

Continuing from http://lists.opensuse.org/opensuse-softwaremgmt/2012-08/msg00000.html At http://lists.opensuse.org/opensuse-factory/2011-11/msg01549.html Duncan said ZYpp should be made lock-free for some operations. How is the work going? There is a list of operations? And then I guess nobody is working in the packagekit backend, true? About that, I would just like to know: - Given that http://en.opensuse.org/openSUSE:Libzypp_API is a bit outdated. What's the best reference for libzypp API? - What happened with the "next-gen API" (http://lists.opensuse.org/zypp-devel/2011-08/msg00018.html and http://lists.opensuse.org/zypp-devel/2012-01/msg00014.html)? https://github.com/openSUSE/zpm looks dead. -- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org To contact the owner, e-mail: zypp-devel+owner@opensuse.org

On Thursday 23 August 2012 14:31:03 Cristian Morales Vega wrote:
Continuing from http://lists.opensuse.org/opensuse-softwaremgmt/2012-08/msg00000.html
At http://lists.opensuse.org/opensuse-factory/2011-11/msg01549.html Duncan said ZYpp should be made lock-free for some operations. How is the work going? There is a list of operations?
As I'm today back from vacation, I'll start to work on this. Target for this is openSUSE Factory. I hope everything except for actual package installation can be done without a hard lock. But it will be quite some work as zypp was not designed that way. Furthermore zypper, pk and yast are not prepared for handling any changes behind their backs. This should also lead to a new API for launching the system and maintaining the repositories, esp. refreshing and syncing them to the pool. The more workflow is provided by zypp the easier it should be to handle concurrency.
And then I guess nobody is working in the packagekit backend, true?
Well, Duncan led me to git@github.com:openSUSE/PackageKit.git and I applied a few fixes there. But frankly it's not obvious to me who's actually maintaining this code, and where. I'm currently thinking about starting to implement a new backend to develop and test the new locks and repo handling. Just to be sure it will fit PK and zyppers needs.
About that, I would just like to know: - Given that http://en.opensuse.org/openSUSE:Libzypp_API is a bit outdated. What's the best reference for libzypp API?
http://doc.opensuse.org/projects/libzypp/HEAD/
- What happened with the "next-gen API" (http://lists.opensuse.org/zypp-devel/2011-08/msg00018.html and http://lists.opensuse.org/zypp-devel/2012-01/msg00014.html)? https://github.com/openSUSE/zpm looks dead.
Maybe the repo handling will be the first step into this direction. -- cu, Michael Andres +------------------------------------------------------------------+ Key fingerprint = 2DFA 5D73 18B1 E7EF A862 27AC 3FB8 9E3A 27C6 B0E4 +------------------------------------------------------------------+ Michael Andres SUSE LINUX Products GmbH, Development, ma@suse.de GF:Jeff Hawn,Jennifer Guild,Felix Imendörffer, HRB16746(AG Nürnberg) Maxfeldstrasse 5, D-90409 Nuernberg, Germany, ++49 (0)911 - 740 53-0 +------------------------------------------------------------------+ -- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org To contact the owner, e-mail: zypp-devel+owner@opensuse.org

On 27 August 2012 18:18, Michael Andres <ma@suse.de> wrote:
On Thursday 23 August 2012 14:31:03 Cristian Morales Vega wrote:
Continuing from http://lists.opensuse.org/opensuse-softwaremgmt/2012-08/msg00000.html
At http://lists.opensuse.org/opensuse-factory/2011-11/msg01549.html Duncan said ZYpp should be made lock-free for some operations. How is the work going? There is a list of operations?
As I'm today back from vacation, I'll start to work on this. Target for this is openSUSE Factory.
I hope everything except for actual package installation can be done without a hard lock. But it will be quite some work as zypp was not designed that way. Furthermore zypper, pk and yast are not prepared for handling any changes behind their backs.
This should also lead to a new API for launching the system and maintaining the repositories, esp. refreshing and syncing them to the pool. The more workflow is provided by zypp the easier it should be to handle concurrency.
And then I guess nobody is working in the packagekit backend, true?
Well, Duncan led me to git@github.com:openSUSE/PackageKit.git and I applied a few fixes there. But frankly it's not obvious to me who's actually maintaining this code, and where.
I'm currently thinking about starting to implement a new backend to develop and test the new locks and repo handling. Just to be sure it will fit PK and zyppers needs.
About that, I would just like to know: - Given that http://en.opensuse.org/openSUSE:Libzypp_API is a bit outdated. What's the best reference for libzypp API?
http://doc.opensuse.org/projects/libzypp/HEAD/
- What happened with the "next-gen API" (http://lists.opensuse.org/zypp-devel/2011-08/msg00018.html and http://lists.opensuse.org/zypp-devel/2012-01/msg00014.html)? https://github.com/openSUSE/zpm looks dead.
Maybe the repo handling will be the first step into this direction.
Knowing this I feel a lot better about all this PackageKit/libzypp stuff. I would like to offer a hand. But without any real experience in C++ or libzypp I can't really help in the definition of a sane API. If at some later stage you need some help with some junior task just ask. -- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org To contact the owner, e-mail: zypp-devel+owner@opensuse.org

On Wednesday 29 August 2012 00:05:32 Cristian Morales Vega wrote:
Knowing this I feel a lot better about all this PackageKit/libzypp stuff. Wait until you see the outcome :)
I would like to offer a hand. Thanks. I'm pretty sure the opportunity will arise.
-- cu, Michael Andres +------------------------------------------------------------------+ Key fingerprint = 2DFA 5D73 18B1 E7EF A862 27AC 3FB8 9E3A 27C6 B0E4 +------------------------------------------------------------------+ Michael Andres SUSE LINUX Products GmbH, Development, ma@suse.de GF:Jeff Hawn,Jennifer Guild,Felix Imendörffer, HRB16746(AG Nürnberg) Maxfeldstrasse 5, D-90409 Nuernberg, Germany, ++49 (0)911 - 740 53-0 +------------------------------------------------------------------+ -- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org To contact the owner, e-mail: zypp-devel+owner@opensuse.org
participants (2)
-
Cristian Morales Vega
-
Michael Andres