Feature changed by: Adrian Schröter (adrianSuSE) Feature #315250, revision 4 Title: Make it easier to move around kiwi files in OBS Buildservice: Implementation Milestone: 2.5 Priority Requester: Mandatory Projectmanager: Mandatory Requested by: Adrian Schröter (adriansuse) Partner organization: openSUSE.org Description: We have often problems when moving around kiwi files in OBS, since they often need a changed repository list then. OBS will support a directive to use the repositories from the project repository definition instead. This can be triggered via defining an "obsrepositories:/" repository in the kiwi file. OBS (and osc) will patch then the kiwi file when a build starts to use the expanded repository list from the project definition. It will work therefore with all kiwi version, but we should add some proper error message to kiwi, if someone tries to run kiwi manually on such a file. Discussion: #1: Adrian Schröter (adriansuse) (2013-06-28 10:18:06) It is half implemented and testable at build-test.opensuse.org. Missing is: * product image support * osc support * correct kiwi error message #2: Robert Schweikert (rjschwei) (2013-06-28 08:48:07) As the feature is partially implemented I guess it is best to move forward with this. However, I think we should re-think this and the existing setup. At present we have: opensuse and obs acronyms comprehended by both KIWI and the build service. With this we get another acronym obsrepositories This acronym however is only comprehended by the build service, if I understand correctly. The build service will change obsrepositories into obs:// with the appropriate path before handing the config file to kiwi. I have the following concerns about this: 1.) We mangle the user data 2.) It is really difficult to explain the difference between obs:/ and obsrepositories:/ 3.) Building images in the build service is getting ever more complicated and drifting father away from a kiwi build on the command line + #3: Adrian Schröter (adriansuse) (2013-06-28 14:57:14) (reply to #2) + we can still drop the entire feature (it is just in the master branch + for now), if there is a better solution. I just do not see one :) + Yes, we mangle the user data, but only when the user decided that we + should do so by using the obsrepositories:/ directive. Please note that + the file in the source repo will be untouched, the mangling does only + happen on the build host. + The general problem here is that the repository list is in the kiwi + file usually while OBS users expect it in the project meta. That is + what I want to solve with the directive. -- openSUSE Feature: https://features.opensuse.org/315250