Feature changed by: Adrian Schröter (adrianSuSE) Feature #315250, revision 7 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. #4: Robert Schweikert (rjschwei) (2013-06-28 10:21:31) (reply to #3) If the actual goal is to have the image build fit better into the concepts prevalent in OBS then it would be easier to tell kiwi to ignore the configured repositories and add new repositories that are taken from the project config on the command line. Thus when OBS invokes kiwi the command line switch --ignore-repos would be use as well as --add-repo, --add-repoalias, --add-repopriority, and --add-repotype. This has the following advantages: 1.) It is very easy to explain and document "During an image build in OBS all repositories configured in the kiwi configuration file will be ignored. Repositories for the image build are added on the kiwi command line and are taken from the project configuration." 2.) It gets OBS out of the business of having to comprehend the repository configuration of the kiwi configuration file 3.) A user can check in a configuration file that will build inside and outside of OBS The only thing that's left to solve in this case is how one build images for multiple distributions in the same project. But this can probably be deducted from some attribute settings. #5: Marcus Schaefer (sax2) (2013-07-01 09:42:11) (reply to #4) I agree, the buildservice has a complete different and unique view on the repository setup. It's better to ignore the information in the . kiwi file in this case instead of changing the user data behind the scene we would also be able to get rid of the obs:// type which confused many people in the past + #6: Adrian Schröter (adriansuse) (2013-07-01 09:50:50) (reply to #4) + We can do that, but that means we need updated kiwi versions for all + distros. Also, we need somewhere some setting if the old or the new way + should be used. Otherwise we would break all old (and current) builds. + What I fear also is that users don't understand then why their + repositories in the kiwi files are ignored. But maybe this can we + solved by some large and loud print lines -- openSUSE Feature: https://features.opensuse.org/315250