Mailinglist Archive: opensuse-buildservice (314 mails)

< Previous Next >
[opensuse-buildservice] osc features for next milestone
  • From: Adrian Schröter <adrian@xxxxxxx>
  • Date: Mon, 7 Jan 2008 11:15:06 +0100
  • Message-id: <200801071115.06800.adrian@xxxxxxx>

Hi all and esp. Peter and Marcus Hüwe :),

I have collected what I think we need in osc for our next milestone in three
month.

Consider this just as a braindump, please comment what makes sense for you and
what not.

* local build support of _link packages
-> this gets currently blocked by needed modularisation in build IIRC.
Peter, please talk directly with Michael how to solve this.

* easy setup of _link + patch packages
A typical usecase / workflow could be this:
- osc co <project> <package>
(maybe support even "osc co <package>" and the server decides from
where to take the package by default. For instance take libqt4 from
KDE:KDE4 project instead of openSUSE:Factory. This would help people
responsible for openSUSE:Factory, because changes arrives there
consolidated by the official maintainers of these components).
- user edits package
- osc ci
-> server refuses, because no write permission in <project>
-> osc offers to create home:<user>/<package>
(optionally create temporary project)
-> osc creates _link + patch file based on user changes
-> osc asks to create a "merge request"
(needs to get supported by server first)
Except for the "merge request", everything should be possible to get
implement without any further server side support.

* After OBS server supports "merge request" handling add support for
following usecases should be supported:
-> list all merge request affecting me (the user)
-> list all merge request affecting this or given project
-> list all merge request affecting this or given package

* merge handling, maybe in this way, just an idea. This would need
the support on server side first:
# osc mergerequests [--project <project>] [--package <package>]
-> osc lists all wanted merge requests with numbers in front
# osc merge [--project <project>] [--package <package>] 2 1 5
-> osc applies merge requests number 2, 1 and 5 in this order.
-> merge should happen on the server side, because it is the same
what the bs_srcserver is doing and we can log what got merged from
whom and when.
So this command does not need any checkout, however it would be nice to
allow this also with checked out packges to avoid the need of
[--project <project>] [--package <package>]
# osc refusemerge 1 9
-> refuse request number 1 and 9
-> osc should ask for a reason statement and send it to the server
# osc mergemove <project> <package> <numbers>
-> modify/forward the merge requests to another project/package.
This is needed for the case like the openSUSE:Factory owner do want an
approval/review from someone/someproject .

Peter, where shall we maintain this document, any wiki page or do you prefer a
text file in svn ? Or do you want to integrate it into something existing ?

There is the merge request document in the wiki, but IIRC we were still
discussing it end of the last year. So this is not final yet and will most
likely change:

http://en.opensuse.org/Build_Service/Concepts/Merge_Request

happy new year !
adrian

--

Adrian Schroeter
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
email: adrian@xxxxxxx

---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-buildservice+help@xxxxxxxxxxxx

< Previous Next >