Mailinglist Archive: zypp-devel (116 mails)
| < Previous | Next > |
[zypp-devel] Re: [PROPOSAL] adaptation of zypp apps to new repo management API
- From: Martin Vidner <mvidner@xxxxxxx>
- Date: Fri, 15 Jun 2007 11:31:17 +0200
- Message-id: <20070615093117.GB19146@xxxxxxxxxxxxxxxx>
On Wed, Jun 13, 2007 at 09:33:58AM +0200, Jan Kupec wrote:
> Yesterday we (Prague YaST team) had a discussion about how to proceed
> with adaptation of YaST to the new repository management API of libzypp.
>
> First thing to note, the API has yet to mature in the upcoming days, as
> we test it with zypper and still modify it as needed. _After_ the API is
> declared done, we propose to proceed as follows:
>
> 1. document transition from old API to the new one (a method to method,
> code to code map) and post to yast-devel.
Here is a start: http://en.opensuse.org/Libzypp/Refactoring/Porting
> 2. drop the old source management code from libzypp trunk
I will now start porting yast2-pkg-bindings and update the abova
page with my experience so that the UI libraries can follow.
> 3. submit libzypp trunk package to BETA (all dependent packages will
> then fail building and maintainers will get the notice).
>
> 4. maintainers of the dependencies adapt their code
>
> 5. after tuning, submit all the stuff to STABLE (in time for the last
> Aplha release)
>
>
> If you are a maintainer of a package affected by the changes in libzypp,
> please provide feedback on the new API as you start looking at it
> (probably after publishing the transition document).
My impression is that zypp did a cleanup of the overbloated
Source_Ref+SourceManager by throwing a lot of things away. If
pkg-bindings need some of it revived, I will take care to add it in
a more structured way.
--
Martin Vidner, YaST developer
http://en.opensuse.org/User:Mvidner
Kuracke oddeleni v restauraci je jako fekalni oddeleni v bazenu
--
To unsubscribe, e-mail: zypp-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: zypp-devel+help@xxxxxxxxxxxx
> Yesterday we (Prague YaST team) had a discussion about how to proceed
> with adaptation of YaST to the new repository management API of libzypp.
>
> First thing to note, the API has yet to mature in the upcoming days, as
> we test it with zypper and still modify it as needed. _After_ the API is
> declared done, we propose to proceed as follows:
>
> 1. document transition from old API to the new one (a method to method,
> code to code map) and post to yast-devel.
Here is a start: http://en.opensuse.org/Libzypp/Refactoring/Porting
> 2. drop the old source management code from libzypp trunk
I will now start porting yast2-pkg-bindings and update the abova
page with my experience so that the UI libraries can follow.
> 3. submit libzypp trunk package to BETA (all dependent packages will
> then fail building and maintainers will get the notice).
>
> 4. maintainers of the dependencies adapt their code
>
> 5. after tuning, submit all the stuff to STABLE (in time for the last
> Aplha release)
>
>
> If you are a maintainer of a package affected by the changes in libzypp,
> please provide feedback on the new API as you start looking at it
> (probably after publishing the transition document).
My impression is that zypp did a cleanup of the overbloated
Source_Ref+SourceManager by throwing a lot of things away. If
pkg-bindings need some of it revived, I will take care to add it in
a more structured way.
--
Martin Vidner, YaST developer
http://en.opensuse.org/User:Mvidner
Kuracke oddeleni v restauraci je jako fekalni oddeleni v bazenu
--
To unsubscribe, e-mail: zypp-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: zypp-devel+help@xxxxxxxxxxxx
| < Previous | Next > |