There is a newer version of the MATE Desktop Environment available at http://pub.mate-desktop.org/releases/1.18/
I'm excited for Mate 1.18, because it's GTK3 only and it might improve HiDPI support. So let us know of any ebuilds/overlay we can test.
*** This bug has been marked as a duplicate of bug 567702 ***
Available in the project repo for early testing
(In reply to NP-Hardass from comment #3) > Available in the project repo for early testing Could we have MATE /etc/X11/xinit/xinitrc.d/ scripts accept DESKTOP_SESSION=MATE ? Several xdm's gets this "wrong" and the scripts fails. See https://bugs.gentoo.org/show_bug.cgi?id=611212 for one example
(In reply to NP-Hardass from comment #3) > Available in the project repo for early testing Please move MATE 1.18 into Gentoo repo, been using the testing repo for weeks now and it works just as well, if not better, than current 1.16
@NP-Hardass, If that's any matter. I can confirm that mate-1.18 from the project repo is running smoothly and I didn't encounter any problems upgrading from 1.16.
I am getting reports here at work about MATE screensaver not working on laptops with external screens in old MATE. MATE 1.16 does not work well with newer gtk+ that recently got stable in Gentoo recently.
(In reply to NP-Hardass from comment #3) > Available in the project repo for early testing The project repo is lagging behind MATE 1.18 now, please update
Nice to the project repo getting some much meed MATE updates, these are are missing though: mate-extra/mate-utils mate-base/mate-applets app-arch/engrampa app-editors/pluma x11-terms/mate-terminal
Any news on this ticket?
(In reply to Joakim Tjernlund from comment #9) > Nice to the project repo getting some much meed MATE updates, these are > are missing though: > > mate-extra/mate-utils > mate-base/mate-applets > app-arch/engrampa > app-editors/pluma > x11-terms/mate-terminal Those updated 1.18.x packages/components are live now: https://gitweb.gentoo.org/repo/gentoo.git/log/x11-terms/mate-terminal/mate-terminal-1.18.1.ebuild https://gitweb.gentoo.org/repo/gentoo.git/log/app-editors/pluma/pluma-1.18.2.ebuild ... not going to exhaustively do the whole list, or even this short list (the ones on this short list are updated, among all the others others which I'm aware of are all bumped, but not yet keyword stabilized. See below.) The usual /etc/portage/package.keywords method is working normally if you want to use or test the various mate 1.18.x packages, and all seems to be working well on gentoo for daily usage (in my personal experience, at least) (In reply to Stephan Litterst from comment #10) > Any news on this ticket? As mentioned on the gentoo keyword stabilization bug: https://bugs.gentoo.org/625838#c2 the upstream MATE bug / issue tracker is showing some outstanding issues. https://github.com/mate-desktop <<< Note that the upstream bugs are tracked per-component / package. If you have some time and a github account, please consider helping MATE (upstream) with additional testing and feedback. This may help move things along for the gentoo keyword stabilization process. (I haven't had time available to poke the upstream tracker myself)
(In reply to kuzetsa from comment #11) > The usual /etc/portage/package.keywords method is working normally if you > want to use or test the various mate 1.18.x packages, and all seems to be > working well on gentoo for daily usage (in my personal experience, at least) Is there a ready-to-use list of packages to unmask? This would save me (and probably others) much time to prepare such a list myself. I my country much of resources related to MATE is blocked by government so it adds to effort to compiling such a list.
Created attachment 514720 [details] /etc/portage/package.keywords/MATE-1.18 (In reply to Alexander Bezrukov from comment #12) > (In reply to kuzetsa from comment #11) > > > The usual /etc/portage/package.keywords method is working normally if you > > want to use or test the various mate 1.18.x packages, and all seems to be > > working well on gentoo for daily usage (in my personal experience, at least) > > Is there a ready-to-use list of packages to unmask? I use these in-tree MATE-1.18 packages: app-arch/engrampa mate-base/caja mate-base/mate mate-base/mate-applets mate-base/mate-control-center mate-extra/mate-netbook mate-extra/mate-utils media-gfx/eom x11-terms/mate-terminal Attachment contains my exact file for unmasking: /etc/portage/package.keywords/MATE-1.18 This will unmask a few dependancies to allow the listed packages to work (you may not need/want all of the ones on this list, but I personally have tested and used them without issues for the past several months) If /etc/portage/package.keywords/ directory does not exist, you can either create it or otherwise make use of the portage man page:$ man portage
(In reply to kuzetsa from comment #13) > Attachment contains my exact file for unmasking: > > /etc/portage/package.keywords/MATE-1.18 > > This will unmask a few dependancies to allow the > listed packages to work (you may not need/want > all of the ones on this list, but I personally > have tested and used them without issues for the > past several months) > Unmasking a larger set of packages will likely be needed unless you also have this entry in: /etc/portage/package.use mate-base/mate -extras -base You will likely need to unmask more packages if you don't have this entry to prevent the mate-base/mate meta package from pulling in extra features and (optional) tools which will need additional testing.
(In reply to kuzetsa from comment #13) > Created attachment 514720 [details] > /etc/portage/package.keywords/MATE-1.18 Thank you. Silly me, I completely forgot about the new portage's autounmask feature which basically does what I want without burdening anybody, recursively.
There is a similar bug (https://bugs.gentoo.org/646896) about mate-1.20.
Is this bug still necessary? Should we not have a 1.18 stabilisation bug by now?
Closing as 1.18 is even stable by now...
