Above pkg installs under /usr/share/themes/Clearlooks-Phenix-3.10-3.12/ but does not change the Name etc. in its index.theme file which make mate-appearance-properties complain that it cannot find the theme. Changing index.theme to: [Desktop Entry] Type=X-GNOME-Metatheme Name=Clearlooks-Phénix-3.10-3.12 Name[fr]=Clearlooks-Phénix-3.10-3.12 Comment=GTK3 port of Clearlooks Comment[fr]=Version GTK3 de Clearlooks Encoding=UTF-8 [X-GNOME-Metatheme] GtkTheme=Clearlooks-Phenix-3.10-3.12 MetacityTheme=Clearlooks-Phenix-3.10-3.12 IconTheme=gnome CursorTheme=DMZ-White CursorSize=16 ButtonLayout=:minimize,maximize,close Makes mate happy again.
hmm, stil learing this but should not clearlooks-phenix:3.10-3.12 replace any previous SLOT(like 3.6)? In that case no name should be changed, instead the install path Clearlooks-Phenix-3.10-3.12 should be the same as previous, just Clearlooks-Phenix Jocke
(In reply to Joakim Tjernlund from comment #1) > hmm, stil learing this but should not clearlooks-phenix:3.10-3.12 > replace any previous SLOT(like 3.6)? > No, that would be misuse of SLOTs.
(In reply to Joakim Tjernlund from comment #0) I think this should be done via a sed-call. Can you provide an ebuild patch?
(In reply to Julian Ospald (hasufell) from comment #2) > (In reply to Joakim Tjernlund from comment #1) > > hmm, stil learing this but should not clearlooks-phenix:3.10-3.12 > > replace any previous SLOT(like 3.6)? > > > > No, that would be misuse of SLOTs. My point is since the theme *replaces* SLOT 3.6 why would you want to keep both? You cannot have both gtk+ versions installed anyway.
(In reply to Joakim Tjernlund from comment #4) > (In reply to Julian Ospald (hasufell) from comment #2) > > (In reply to Joakim Tjernlund from comment #1) > > > hmm, stil learing this but should not clearlooks-phenix:3.10-3.12 > > > replace any previous SLOT(like 3.6)? > > > > > > > No, that would be misuse of SLOTs. > > My point is since the theme *replaces* SLOT 3.6 why would you > want to keep both? > You cannot have both gtk+ versions installed anyway. This is what I think: Add a clearlooks USE flag to gtk+:3.x which will PDEPEND on clearlooks-phenix-3.X where X matches the corresponding gtk+:3.x Remove the SLOTs on all clearlooks-phenix Now everything will just work and clearlooks wil follow gtk+ version.
(In reply to Joakim Tjernlund from comment #5) > (In reply to Joakim Tjernlund from comment #4) > > (In reply to Julian Ospald (hasufell) from comment #2) > > > (In reply to Joakim Tjernlund from comment #1) > > > > hmm, stil learing this but should not clearlooks-phenix:3.10-3.12 > > > > replace any previous SLOT(like 3.6)? > > > > > > > > > > No, that would be misuse of SLOTs. > > > > My point is since the theme *replaces* SLOT 3.6 why would you > > want to keep both? > > You cannot have both gtk+ versions installed anyway. > > This is what I think: > > Add a clearlooks USE flag to gtk+:3.x which will > PDEPEND on clearlooks-phenix-3.X where X matches > the corresponding gtk+:3.x > Remove the SLOTs on all clearlooks-phenix > > Now everything will just work and clearlooks wil follow > gtk+ version. I don't think gtk+ should have random use flags for themes. It's a library.
(In reply to Julian Ospald (hasufell) from comment #6) > (In reply to Joakim Tjernlund from comment #5) > > (In reply to Joakim Tjernlund from comment #4) > > > (In reply to Julian Ospald (hasufell) from comment #2) > > > > (In reply to Joakim Tjernlund from comment #1) > > > > > hmm, stil learing this but should not clearlooks-phenix:3.10-3.12 > > > > > replace any previous SLOT(like 3.6)? > > > > > > > > > > > > > No, that would be misuse of SLOTs. > > > > > > My point is since the theme *replaces* SLOT 3.6 why would you > > > want to keep both? > > > You cannot have both gtk+ versions installed anyway. > > > > This is what I think: > > > > Add a clearlooks USE flag to gtk+:3.x which will > > PDEPEND on clearlooks-phenix-3.X where X matches > > the corresponding gtk+:3.x > > Remove the SLOTs on all clearlooks-phenix > > > > Now everything will just work and clearlooks wil follow > > gtk+ version. > > I don't think gtk+ should have random use flags for themes. It's a library. OK, but there is only meant to be one Clearlooks-Phenix installed at any one time and it should match the installed GTK+3.x version. How about: Remove all SLOTs and add blockers to match given gtk+3.x lib. Then, hopfully, portage will do the rigth thing? If blockers wont work, just make sure to stabilize Clearlooks-Phenix as gtk+3.x is stablized.
(In reply to Joakim Tjernlund from comment #7) > How about: > Remove all SLOTs and add blockers to match given gtk+3.x lib. > Then, hopfully, portage will do the rigth thing? > > If blockers wont work, just make sure to stabilize Clearlooks-Phenix as > gtk+3.x is stablized. Yes, that's the only one alternative and will regularly cause weird blockers for users, since gtk+ and clearlooks-phenix are not always synchronous and there is no way to make them, unless you are upstream yourself. Currently people are able to use an incompatible clearlooks-phenix version with a bleeding-edge gtk+:3 version. Not everything might work, but it's better than no theme for most. If we go hardline for the deps, that won't work anymore.
(In reply to Julian Ospald (hasufell) from comment #8) > (In reply to Joakim Tjernlund from comment #7) > > How about: > > Remove all SLOTs and add blockers to match given gtk+3.x lib. > > Then, hopfully, portage will do the rigth thing? > > > > If blockers wont work, just make sure to stabilize Clearlooks-Phenix as > > gtk+3.x is stablized. > > Yes, that's the only one alternative and will regularly cause weird blockers > for users, since gtk+ and clearlooks-phenix are not always synchronous and > there is no way to make them, unless you are upstream yourself. > > Currently people are able to use an incompatible clearlooks-phenix version > with a bleeding-edge gtk+:3 version. Not everything might work, but it's > better than no theme for most. If we go hardline for the deps, that won't > work anymore. Right, better than the current SLOTs anyway. Just remove them and stablize clearlooks-phenix-5.0.7 and we are good to go.
Created attachment 392872 [details] clearlooks-phenix ebuild i SLOT 0
(In reply to Joakim Tjernlund from comment #10) > Created attachment 392872 [details] > clearlooks-phenix ebuild i SLOT 0 Added my own ebuild as a stopgap fix until resolved in Gentoo
Ping? Clearlooks is just broken now and something needs to be done.
16 Apr 2015; Ian Delaney <idella4@gentoo.org> clearlooks-phenix-5.0.7.ebuild, clearlooks-phenix-6.0.3.ebuild: clearlooks-phenix-5.0.7.ebuild brought in line with vrsn 6.0.3 *clearlooks-phenix-6.0.3 (16 Apr 2015) 16 Apr 2015; Ian Delaney <idella4@gentoo.org> +clearlooks-phenix-6.0.3.ebuild, -clearlooks-phenix-3.0.16.ebuild, clearlooks-phenix-5.0.7.ebuild, metadata.xml: bump; patch by new proxy maintainer, metadata updated accordingly, all wrt bug #533228, rm old version 3.0.16
