[opensuse-artwork] Yast2-theme package
Hi, I am currently solving issue with yast2-theme for SLE and it will also affect yast2-theme-openSUSE, so I would like at first discuss problems and my proposed solutions. Please CC me if you answer as I am not subscribed to opensuse-artwork mailing list. 1) yast2-theme create link to opensuse yast icons to high-res directory - https://github.com/yast/yast-theme/blob/master/package/yast2-theme.spec#L112 It is problem because in SLE it also have links to opensuse, which is wrong. My proposed solution is to create two additional rpm spec files - yast2-theme-openSUSE.spec for yast2-theme-openSUSE including crystal and oxygen theme and yast2-theme-SLE.spec for SLE related theming and both contain links to proper directory and conflict each other. 2) yast2-x11 contain file for installation icewm style. It is problem as now SLE have more dark style, so it cause difference in this package, that is not intended to be used on for theming, only for X11 setup in installation. My proposed solution is after we solve 1) to move icewm conf file to yast2-theme-{openSUSE,SLE} and keep it separated. 3) yast2-theme for opensuse partially lives at https://github.com/yast/yast-theme and partially at https://github.com/openSUSE/branding/tree/13.2/yast I think it do not make sense to have it at two places and we should merge it. I propose to use yast-theme file as SLE already have all theming for installation and yast here and also we have automatic deployment here, so when you modify master, it automatic goes to opensuse. I can add people to have write permissions there. Thanks Josef -- To unsubscribe, e-mail: opensuse-artwork+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-artwork+owner@opensuse.org
Am 28.02.2014 13:58, schrieb Josef Reidinger:
I think it do not make sense to have it at two places and we should merge it. I propose to use yast-theme file as SLE already have all theming for installation and yast here and also we have automatic deployment here, so when you modify master, it automatic goes to opensuse. I can add people to have write permissions there.
It does make sense to have all branding stuff together and it makes sense to have all yast stuff together - so somewhere there has to be a split, or we would have everything of openSUSE in one git repo. Greetings, Stephan -- Ma muaß weiterkämpfen, kämpfen bis zum Umfalln, a wenn die ganze Welt an Arsch offen hat, oder grad deswegn. -- To unsubscribe, e-mail: opensuse-artwork+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-artwork+owner@opensuse.org
On 28 February 2014 13:58, Josef Reidinger <jreidinger@suse.cz> wrote:
Hi, I am currently solving issue with yast2-theme for SLE and it will also affect yast2-theme-openSUSE, so I would like at first discuss problems and my proposed solutions. Please CC me if you answer as I am not subscribed to opensuse-artwork mailing list.
1) yast2-theme create link to opensuse yast icons to high-res directory - https://github.com/yast/yast-theme/blob/master/package/yast2-theme.spec#L112 It is problem because in SLE it also have links to opensuse, which is wrong.
My proposed solution is to create two additional rpm spec files - yast2-theme-openSUSE.spec for yast2-theme-openSUSE including crystal and oxygen theme and yast2-theme-SLE.spec for SLE related theming and both contain links to proper directory and conflict each other.
2) yast2-x11 contain file for installation icewm style. It is problem as now SLE have more dark style, so it cause difference in this package, that is not intended to be used on for theming, only for X11 setup in installation.
My proposed solution is after we solve 1) to move icewm conf file to yast2-theme-{openSUSE,SLE} and keep it separated.
3) yast2-theme for opensuse partially lives at https://github.com/yast/yast-theme and partially at https://github.com/openSUSE/branding/tree/13.2/yast
I think it do not make sense to have it at two places and we should merge it. I propose to use yast-theme file as SLE already have all theming for installation and yast here and also we have automatic deployment here, so when you modify master, it automatic goes to opensuse. I can add people to have write permissions there.
Hi Josef, sorry for taking so long to get back to you. I understand why having files and folders named 'openSUSE' in SLE would be wrong, but I'm not sure I we need to go as far as you propose separating the two of them. Would there be any issue renaming the files and folders in question from openSUSE to 'SUSE' or some other 'neutral' name that makes sense for our common heritage? My problem with your proposals is I feel like they'd increase the maintenance burden down the road, especially with the general goal of keeping SLE and openSUSE closer together for the benefit of both distros Thanks - Richard
Thanks Josef -- To unsubscribe, e-mail: opensuse-artwork+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-artwork+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse-artwork+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-artwork+owner@opensuse.org
participants (3)
-
Josef Reidinger
-
Richard Brown
-
Stephan Kulow