Dne 11. 12. 19 v 15:39 Stefan Hundhammer napsal(a):
Only for the very first of those PRs there is a realistic chance for a green Travis build; for all subsequent ones, there is only the (now outdated) docker image that also includes those libyui packages. That image needs to be rebuilt, but that fails because now there is a libyui with a higher SO number, but no matching libyui-something packages.
That's partly caused by the circular dependency libyui <-> libyui-<something>...
So the only way out is to brute-force merge despite red Travis and hope for the best. And to do this a couple of times until it gets green in Jenkins and in OBS.
Yes, that's ugly...
Would it be better to have one large libyui repo that contains the base libyui, and also most of the others (except libyui-gtk* ?) and create all the binary packages that we have now from that single source repo?
We could include all plugins if we allow building only some parts, e.g. we would skip the Gtk plugins, some other distribution could skip the *-pkg (libzypp) plugins, etc... If you could easily configure which parts you want to build then it should be OK I think.
Or is there some killer argument against this?
For me it looks like a quite good idea. We just need to do some research or maybe try it to find the drawbacks. And as Josef pointed out, we should check how the other projects solve this, we do not need to reinvent the wheel... -- Best Regards Ladislav Slezák Yast Developer ------------------------------------------------------------------------ SUSE LINUX, s.r.o. e-mail: lsle...@suse.cz Lihovarská 1060/12 tel: +420 284 028 960 190 00 Prague 9 fax: +420 284 028 951 Czech Republic http://www.suse.cz/ -- To unsubscribe, e-mail: yast-devel+unsubscr...@opensuse.org To contact the owner, e-mail: yast-devel+ow...@opensuse.org
