On Wed, 11 Sep 2013 15:17:24 +0200
Arvin Schnell
On Wed, Sep 11, 2013 at 02:58:32PM +0200, Josef Reidinger wrote:
testing: current it test only changes in master branch. How important for you if we automatic test also pull requests and maintenance branches? Related question is how important for us is to have generated <package>.spec file as it quite block more generic solutions.
Automatic pull requests for branches would be nice. Packaging for old distros usually requires a development system for that distro.
Yes, problem is that we need it even now for each branch and I would like to reduce need of such environment or better do it automatic. And one idea is to use osc which can build in chroot. But osc need already spec file.
Generating the spec file looks like a must to me. Manual editing VERSION and LIBVERSION changes is error-prone.
Generating spec file is slightly against previous idea as you need proper version of devtools to generate proper spec file. If problem is really only VERSION and LIBVERSION update, then we can solve it by some kind of seding during making package ( so spec is automatic update when you call make package ). Or is there more things we need to generate?
autosubmit: Are you satisfied with current autosubmit to Yast:Head? And what about automatic submit to factory? What is criteria to submit to Yast:Head and to factory? Do you want it automatic or some someautomatic or manual step is better from your POV?
I never know whether the autosubmit to factory works. Right now I'm expecting submitrequests but there aren't any. I have no idea where to look for a status or problem.
Me neither, I try to write email to thomas so we know where it is located and can manage it.
The build node (for YaST:Head) should use packages from openSUSE:Factory. E.g. libbtrfs-devel is not available in 12.3 but required for yast2-snapper now.
If we use idea above ( original author is lslezak ), then osc in its chroot install everything it need with proper target ( so in your case factory ). At first I would like collect requirements and then we can discuss how to make it on workshop. Josef
Regards, Arvin
-- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org