Re: ALP Git-Packaging-Workflow group created
On Donnerstag, 21. Juli 2022, 09:34:17 CEST Jan Engelhardt wrote:
On Wednesday 2022-07-20 16:37, Dirk Müller wrote:
I would make the case that OBS history is not particularly interesting for its _messages_ [..]
[.. ]There are some suggestions around using git notes for the end-user changelog, but that hasn't been evaluated in detail yet. Any suggestions or input welcome.
Adam Majer held a conversation with a few individuals ahead of the openSUSE conf 2022 for thoughts, I'd like to repaste some of that since it was originally off-list and still hope to see this coming to build.opensuse.org soon.
---
Date: Tue, 31 May 2022 15:33:31 +0200 From: Jan Engelhardt To: adamm Cc: stroeder
On Tuesday 2022-05-31 12:50, Adam Majer wrote:
https://build.opensuse.org/project/show/devel:ALP https://code.opensuse.org/adrianSuSE/Alp https://code.opensuse.org/adrianSUSE/zypper https://code.opensuse.org/package/zypper
Internally, most of the feedback from maintainers I've talked to is along the lines of "ok, so I'll have to adapt to this I guess", ie. not enthusiastic :-)
I would like to get your thoughts about this and any suggestions of what you would expect this "new" approach to have.
* Because the git checkout does not have the .osc directory, the osc build line is a bit longer than usual.
osc build --alternative-project openSUSE:Factory standard x86_64 pdns.spec
the current osc can checkout a scmsync package. You get a local git clone, but osc remains working with local builds inside. The downside atm is that it still creates a .osc which need to be ignored by git. I hope we will find a better solution for that in future. Try osc co home:adrianSuSE:OBSGIT git-example-1 for an example package which defines a git url. At least osc-0.179 is required for this though.
* Checking out /package/zypper: the tarball is a (dangling) symlink to /ipfs.
ALP is "just" a spin/a distribution -- let's deploy this git scheme for an "actual" development prj and see how that works out. I could think of a few to spare for the experiment that have low volume (security:netfilter, maybe network:telephony).
Also, any sticking points when it comes to current (current OBS) workflow that git could improve?
* Some command-line equivalent for `osc sr` will be needed if git is used as a backend. `git push` to /jengelh/zypper is (would be) easy, but making the actual SR/MR/PR.. if I don't know better, would require opening a browser, and one shouldn't have to go to a browser.
A sr would not transfer the git information atm (and on purpose). That means
you can work with such a git setup in your devel or home project and submit
request the result to factory for example.
However, the long term plan here is that the sr gets actually replaced by a pull
request in the git hosting instance.
--
Adrian Schroeter
participants (1)
-
Adrian Schröter