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. 2. drop the old source management code from libzypp trunk 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). Cheers, jano -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org