I guess I can try updating this but my employer has since changed to use openVPN so I won't be able to test things as I did before.

Move the homepage entry to right after sources in package.yml.

Add MAINTAINERS.md

Add MAINTAINERS.md

Undo editor formatting.

@JoshStrobl The symlink /etc/xprofile is now removed. lightdm will source /usr/share/defaults/etc/xprofile, as well as /etc/xprofile and $HOME/.xprofile if they exist. Once you patch gdm and sddm in the same way, the three display managers should behave in a consistent manner.

I made lightdm source the vendor-provided xprofile and removed the symlink of /etc/xprofile to /usr/share/defaults/etc/xprofile for a stateless setup.

Make lightdm source /usr/share/defaults/etc/xprofile for a stateless setup.

Do not symlink to /usr/share/defaults/etc/xprofile.

Revert last change.

Remove symlink to /usr/share/defaults/etc/xprofile.

@JoshStrobl I will remove the symlink line and update the other patch accordingly (line 34). So I guess we should not land this until that is done.

@ermo Yeah I totally understand that. There is no pressure from me on you and the Core team. I believe this will eventually get resolved.

@ermo I made some modifications to D8989 based on your suggestions. I do think this is a better way to organize things.

Add system-wide xprofile and user-specific xprofile.

@ermo That sounds a good idea. One question is which package /usr/share/defaults/etc/xprofile goes to? Still baselayout or some other package?

@ermo Yeah understood. If there is anything else I can do to improve the current package, just let know.

@ermo I went ahead and created D8989 for adding default xprofile. Let me know if you have any suggestions.

Forgot to bump release.

@ermo I also cooked up a .xprofile and tested it on all four DEs. My question is, how should I proceed to create a patch for that? Should I create a patch for baselayout? My concern is that I have no way to test whether the new baselayout package works as intended.

@ermo I have moved the part of loading key maps out of lightdm-wrapper so I think this D8984 is ready for review again.

Remove code which sources key maps and xsessions. Only source .profile, .xprofile and .Xresources.

@ermo Yeah I actually looked into the xsession startup script shiped with gdm and sddm. They both source .Xresources along with .profile and .xprofile. lightdm-wrapper will do the same if this patch gets merged.

In response to @ermo's comment in D8678 about setting up the same procedure for other Xsessions, I confirmed that .profile and .xprofile is automatically picked up by gdm and sddm so no changes are needed for those two.

This seems a duplicate of T8859. Feel free to close it as I can't figure out how to close it as a duplicate of another issue.

In D8904#145228, @JoshStrobl wrote:

That doesn't resolve my marked issue of it being a step. It should be environment : |
Example: R485 package.yml:70

Add a pipe symbol to the environment block.

Move definitions of environment variables to the environment block.

Fix bash autocompletion for bazel.

@livingsilver94 The issue is that bazel binary is never supposed to be stripped. And when we build it locally, we don't strip it, that is why we can build projects using our locally generated eopkg file. However, the build server will automatically strip debug symbols from the binary and that will break the package. So we have to add debug: no to tell the server explicitly not to strip the debug symbols.

Was able to build bazel again after some fiddling. Submitted patch D8904. So assign the task to myself for now.

Assign to @livingsilver94 since he was the one who updated bazel most recently.

Rebuild the package after updating the desktop file