From: gorkawien <gorkawien@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Request: Please include gnome gnome-menus and gnome-screensaver as dependency from metapackage "gnome"
Date: Sat, 11 Jul 2020 00:21:00 +0200 [thread overview]
Message-ID: <20200710222100.Cl9iTUo0_t_YJtMqSNZanGqF6RFXEw2kDcto4oYJWM8@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-23513@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1060 bytes --]
New comment by gorkawien on void-packages repository
https://github.com/void-linux/void-packages/issues/23513#issuecomment-656919320
Comment:
@ericonr is not about the size. I am building a live iso of Gnome, and i think that the GDM package is causing me trouble with lightdm. and other DMs
The reason to use lightdm is because the RAM drops around 200 -250 MB.
The issue I have noticed is that with another DM the anon login doesnt work, only root.
I also notice that eog, evince, and file-roller are dependencies.
IMHO this 3 packages should be a dependency , and if they are, also gnome-terminal should be a dependency.
@mnabid thanks for the information. Is good to know that they are considering including gnome-menus.
Maybe I didn't explain myself clear. My personal opinión is that no DM should be included as dependency in the metapackage (let the user choose).
Also I would also remove the dependencies of eog, file-roller and evince, but of course gnome-menus is more important.
Thanks also for information regarding gnome-screensaver.
next prev parent reply other threads:[~2020-07-10 22:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-10 19:14 [ISSUE] " gorkawien
2020-07-10 19:45 ` ericonr
2020-07-10 20:37 ` mnabid
2020-07-10 22:21 ` gorkawien [this message]
2020-07-10 23:16 ` pullmoll
2020-07-12 0:27 ` mnabid
2020-07-18 9:39 ` ProjectMoon
2021-01-22 1:08 ` ericonr
2021-01-22 1:08 ` [ISSUE] [CLOSED] " ericonr
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200710222100.Cl9iTUo0_t_YJtMqSNZanGqF6RFXEw2kDcto4oYJWM8@z \
--to=gorkawien@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).