masking GDM >3.17.2 (or patching it) if using startx otherwise faking its presence if not

But what if you want to use GNOME without systemd and with basic functionality?

Simple, you utilize my patchset which I assisted Funtoo Linux in officially implementing from GNOME 3.12 to 3.16. It reintegrates support for everything but Wayland. Until recently, practically the only way for Gentoo Linux users to enjoy a similar experience was to utilize Sakaki'sfuntoo-2-gentoo shim overlay. This is no longer the case as I have decided to extend support to Gentoo Linux directly through the GNOME Without Systemd project. Those seeking background information (such as the description of the project, my rationale for creating it, the length of long-term support, the frequency of updates and so forth) can begin with the Introduction while those wanting to jump right in can skip ahead to Getting Started. If you have any trouble, feel free to contact me directly.

In short, my patchset aside, anyone telling you that choosing GNOME means choosing systemd is wrong. Granted, one day, GNOME may really and truly depend on systemd, but that day is not today. So in the meantime, for Gentoo and Funtoo Linux users who still desire in a choice in how they run GNOME, they have one.

..
..my patchset ..reintegrates support for everything but Wayland. Until recently, practically the only way for Gentoo Linux users to enjoy a similar experience was to utilize Sakaki'sfuntoo-2-gentoo shim overlay. This is no longer the case as I have decided to extend support to Gentoo Linux directly through the GNOME Without Systemd project.

In short, my patchset aside, anyone telling you that choosing GNOME means choosing systemd is wrong. Granted, one day, GNOME may really and truly depend on systemd, but that day is not today. So in the meantime, for Gentoo and Funtoo Linux users who still desire in a choice in how they run GNOME, they have one.

Great job! :-)

tw04l124 wrote:

I think I prefer setting those useflags myself as to rely on a preset which I may not need in the first place...

It's the same as setting your profile to desktop/anything-else; you can still override globally or on a per-package basis.
The defaults just tend to be well-tested by the upstream ebuild or overlay maintainer, as well as other users.

Is there a difference between your overlay and the funtoo overlay? this forum post it says funtoo comes with this overlay, but on your github guide there are steps to add it to funtoo. I'm currently using funtoo, and gnome is in the repository and available without systemd, but version 3.16 isn't available. If it's the same overlay, is there a reason for 3.16 not being available?

As for Fallback Mode, it was dropped in GNOME 3.8. What they have now is GNOME Classic.

steveL wrote:

[...]
Great job!

Thanks.

keitho2000 wrote:

Is there a difference between your overlay and the funtoo overlay? this forum post it says funtoo comes with this overlay, but on your github guide there are steps to add it to funtoo. I'm currently using funtoo, and gnome is in the repository and available without systemd, but version 3.16 isn't available. If it's the same overlay, is there a reason for 3.16 not being available?

Yes, there is a difference between my overlay and Funtoo's overlay. My overlay:

is compatible with both Gentoo and Funtoo linux

always has the latest version of my patchset

easily supports switching between GNOME release versions

Furthermore, Funtoo's GNOME overlay is not directly derived from mine. They have an earlier version of my patchset which was manually integrated and which they are independently maintaining. If you check FL-2485 on their bug tracker, I already gave them the information they need to implement GNOME 3.16 however they wish. Perhaps they are still reviewing things?_________________Dantrell B.

thank link uses systemd, and other services which are not really essential and drives up memory consumption

And i prefer the memory value x-screensaver + nvidia-binary-gpu blob after entered password to the log in manager ..
I also saw top and htop have different memory footprints which should be considered too.

that stuff looks like in the good old gnome 2 days ...

Last edited by Roman_Gruber on Sun Jul 19, 2015 8:25 am; edited 2 times in total

Hi, so on the VirtualBox VM I use for testing dantrell's overlays, after a 3.16 install (based on a vanilla handbook ~amd64 system, per these instructions), emerge --depclean wants to remove (inter alia) dev-lang/nasm-2.11.08 and media-fonts/liberation-fonts-2.00.1-r1.

The other packages that you mention (mkfontscale etc) are not installed (on my system) to begin with. If I then go through with the emerge --depclean and reboot, the system comes up fine into GNOME 3.16.

So yes, I think you should be fine to unmerge the list of packages cited._________________Regards,

Hi, i got another problem with nautilus, when i use the new dropdown menu to change the view (icon or list). the nautilus freeze and ended...
I have tried to recomplie it but still same happen. do you have this problem? Thanks!

Yes, just tried this: nautilus freezes when the view toggle dropdown is used for me also, on 3.16.
This occurred on my VM build both before and after the depclean (I have snapshots either side), so that's not the issue.
The view can be switched OK on nautilus on GNOME 3.14, no freeze._________________Regards,

Hi, i got another problem with nautilus, when i use the new dropdown menu to change the view (icon or list). the nautilus freeze and ended...
I have tried to recomplie it but still same happen. do you have this problem? Thanks!

Sakaki wrote:

Yes, just tried this: nautilus freezes when the view toggle dropdown is used for me also, on 3.16.
This occurred on my VM build both before and after the depclean (I have snapshots either side), so that's not the issue.
The view can be switched OK on nautilus on GNOME 3.14, no freeze.

Sakaki, thanks for verifying the issue. However, since it isn't related to my patchset, it should really be reported elsewhere. Although my guess is that it already has been and may even be resolved with Nautilus commit 394fde4 (which hasn't been backported to 3.16 yet).

Still, I will be happy resolve this issue on my end if it isn't handled in a reasonable amount of time._________________Dantrell B.

For those interested in using Dantrell's overlays in Gentoo, I have just extended my EFI Install Guide to include instructions for installing GNOME 3 under OpenRC (the default systemd instructions are also retained, of course).

As before, those looking for shorter-form instructions should look instead at the GNOME without systemd wiki entry._________________Regards,

just wanted to say THANKS to dantrell and Sakaki for the ability to run GNOME & co. w/o systemd! for quite a while i have been stuck with crazy package.{use,keywords,mask} settings in order to keep using Evolution 2.32 w/o GNOME+systemd. eventually it just stopped working and screwed up my system. regardless, while i have not installed all of GNOME 3, i can report that GNOME 3 apps like Evolution work fine with this setup. in particular i followed Sakaki's https://wiki.gentoo.org/wiki/GNOME/GNOME_Without_systemd guide.

this also has made me learn a little about Funtoo, which seems worth a closer look.

i did have 1 question: is it necessary to activate the dantrell-gnome:default/amd64/3.16 profile if i am not installing all of GNOME 3? so far it seems to be willing to update w/o the profile selected?

i did have 1 question: is it necessary to activate the dantrell-gnome:default/amd64/3.16 profile if i am not installing all of GNOME 3? so far it seems to be willing to update w/o the profile selected?

The bundled profiles are there to expedite matters for a default install.

If you have unique requirements (such as a partial install), then in lieu of activating a profile, you simply have to manage the relevant configuration yourself in /etc/portage/*._________________Dantrell B.

Quick update - Dantrell B has now made a patchset for GNOME 3.18 available (in addition to 3.14 and 3.16, which remain supported). I have tried emerging this under ~amd64 and it works fine (for me).

I've modified the Gentoo wiki page GNOME Without systemd to reflect the availability of this new version. I have also (for those interested in more 'end-to-end' system install instructions) updated the OpenRC track of my EFI Install Guide, and added a corresponding 3.18 profile to the dantrell-gnome-reparent overlay, for those who use this.

PS 3.18 does not appear to have the 'Nautilus freeze on list/icon toggle' issue which has impacted some users of 3.16 under OpenRC._________________Regards,

another quick update: Dantrell is now providing a set of 'extended' profiles (in addition to his existing, 'regular' variants, which remain supported) for each of GNOME 3.14, 3.16 and 3.18, as part of his patchset.

These new profiles provide a close USE-flag match to their familiar Gentoo desktop/gnome cousins, and (happily!) make my dantrell-gnome-reparent profiles redundant.

As such, users of the dantrell-gnome-reparent profiles (for example, those who have installed GNOME on OpenRC using my EFI Install Guide (OpenRC track)), should migrate now to the corresponding 'extended' Dantrell profile.

For example, if you were using dantrell-gnome-reparent:default/linux/amd64/13.0/desktop/gnome/3.14, you should sync all your overlays, then issue:

Hi and thanks for your hard work. I've noticed the "deprecated-background" useflag in gnome-shell and mutter, 3.18 branch, but it seems the patches are missing from the repo. Does it mean this useflag is deprecated or the patch files were simply forgotten?

Hi and thanks for your hard work. I've noticed the "deprecated-background" useflag in gnome-shell and mutter, 3.18 branch, but it seems the patches are missing from the repo. Does it mean this useflag is deprecated or the patch files were simply forgotten?

The patches aren't missing, they are just referenced incorrectly in the ebuilds which prevents them from applying (besides, the patches are incomplete). The USE flag isn't deprecated either, I just use that word as a prefix to mean that the codepaths they relate to are deprecated upstream and not that I deprecated them.

The patches aren't missing, they are just referenced incorrectly in the ebuilds which prevents them from applying (besides, the patches are incomplete). The USE flag isn't deprecated either, I just use that word as a prefix to mean that the codepaths they relate to are deprecated upstream and not that I deprecated them.