Created attachment 319212 [details] Contains ebuild + files for mdm Hello, the Linux Mint folks have forked the gnome display manager 2.20, improved upon it, and renamed it to MDM. Source: linuxmint.com/rel_maya_whatsnew.php Since no ebuild for it was available I used the gdm-2.20.11-r1.ebuild as base to create the live ebuild mdm-9999.ebuild. Some renaming changes had to be done (ebuild and patches) but so far it works, and adding "mdm" into /etc/conf.d/xdm makes the display manager start successfully. The git repository of the project can be viewed online here: https://github.com/linuxmint/mdm Attached are the necessary files to extract into a local portage overlay. Regards, Philipp Richter.
Hello, have you tried to use the 1.0.6 and 1.0.7 release tags? Michael
Created attachment 367844 [details] mdm-1.4.9.ebuild Updated ebuild to current release version. Changes include; blocker on gdm-2 due to file conflicts in gtk modules, Xdmcp support has been removed, patch file gdm-2.20.9-parallel-make.patch no longer needed, added webkit:2 requirement for HTML greeter. Refinement thoughts; running autogen.sh is a bit ugly, default HTML theme not included and no release version yet only git (only at https://github.com/linuxmint/mdm-themes).
Would be nice to have the MDM DISPLAY MANAGER on portage Thanks
(In reply to Palme from comment #3) > Would be nice to have the MDM DISPLAY MANAGER on portage > or at least Updated ebuild to current release version. some Changes are Add explicit support for cinnamon-screensaver Fixed 24h clock support Gave all greeters the same background color/image settings (also fixes focus issues for mdmwebkit in multi-monitor setup) Updated comments in mdm.conf and defaults file, added syslog support Multi-monitor support etc.. > Thanks
Could we get this in portage as replacement for the retired gdm-2.x?
Is anyone willing to be a proxied maintained for this? https://wiki.gentoo.org/wiki/Project:Proxy_Maintainers
Created attachment 400828 [details] mdm-1.8.3.ebuild This ebuild compiles and works on my local machine. Could a dev please review this ebuild and suggest some improvements if needed?
Created attachment 400830 [details] files-mdm-1.8.3
Created attachment 430066 [details] mdm-2.0.7.ebuild I updated the previous ebuild for 2.0.7 and it appears to be working for me. I should warn everyone that this is the first time I have even looked inside an ebuild file so it is very possible that things are not correct. I also applied what I think is a somewhat "dirty fix". When running the old ebuild (or the new one without my fix) I got the error: [code]automake-1.15: error: cannot open < gnome-doc-utils.make: No such file or directory[/code] so I applied my fix in the ebuild just before it ran ./autogen.sh [code] gnomedocdir=$(locate gnome-doc-utils) cp $gnomedocdir ./ [/code] While this works I think it is bad because a) ./ should be a variable but I don't know what that is b) I should not really have to do this at all. Maybe gnome-doc-utils.make should be in the path? I am willing to try to get this ebuild to a good presentable state and then maybe continue to maintain it after that but I would like some help learning how to properly write ebuilds from someone with more experience.
Comment on attachment 430066 [details] mdm-2.0.7.ebuild I updated the previous ebuild for 2.0.7 and it appears to be working for me. I should warn everyone that this is the first time I have even looked inside an ebuild file so it is very possible that things are not correct. I also applied what I think is a somewhat "dirty fix". When running the old ebuild (or the new one without my fix) I got the error: automake-1.15: error: cannot open < gnome-doc-utils.make: No such file or directory so I applied my fix in the ebuild just before it ran ./autogen.sh gnomedocdir=$(locate gnome-doc-utils) cp $gnomedocdir ./ While this works I think it is bad because a) ./ should be a variable but I don't know what that is b) I should not really have to do this at all. Maybe gnome-doc-utils.make should be in the path? I am willing to try to get this ebuild to a good presentable state and then maybe continue to maintain it after that but I would like some help learning how to properly write ebuilds from someone with more experience.
