Talk:Enlightenment

Note
Before creating a discussion or leaving a comment, please read about using talk pages. To create a new discussion, click here. Comments on an existing discussion should be signed using ~~~~:

A comment [[User:Larry|Larry]] 13:52, 13 May 2024 (UTC)
: A reply [[User:Sally|Sally]] 11:44, 5 November 2024 (UTC)
:: Your reply ~~~~

Additional applications

Talk status

This discussion is done.

Let's punt this section to a separate page, which will be useful for users of other WMs and lightweight DEs as well. — yngwin 06:47, 4 July 2012 (UTC)

I agree, this section has not much to with the WM. It would make it more concise. Needle 19:14, 18 September 2012 (UTC)

Done, since we now have Recommended applications. — yngwin (wiki admin) (talk) 05:27, 19 September 2012 (UTC)

Old version

Talk status

This discussion is done.

User astaeker edited this article right out from under me while I was trying to follow it. Now, I have it halfway installed with layman, and the instructions for completion of the installation are gone! Tim Cuthbertson 18:14 UTC 18 Sep, 2012

Sorry. You can use the "history" tab to view old version. here is the last one before my edit.

Astaecker 18:37, 18 September 2012 (UTC)

Review of ebuilds and modules since 2012dec24 update needed

Talk status

This discussion is done.

Some of these ebuilds do not seem to be available anywhere (e.g., dev-util/editje). Also I can't seem to find any modules in portage, but the seem to exist in the enlightemet overlay (of which much has been masked). I don't understand the make.conf ENLIGHTENMENT_MODULES="" section either -- is there documentation somewhere else on this?

Install section updated, sets removed. — Tommy[D] 16:58, 27 December 2012 (UTC)

Move Tips and Tricks to its own place

Talk status

This discussion is done.

For starting enlightenment from the console, a simple "enlightenment_start" entry in ~/.initrc is enough, everything else is additional stuff, which might be usefull for other window manager too. — Tommy[D] 17:29, 27 December 2012 (UTC)

It has been done, Enlightenment#Tips_and_tricks

Juippis (talk) 12:39, 23 June 2020 (UTC)

E18

Talk status

This discussion is done.

Enlightenment E18. By checking blog, it should be in "stabilization state", could we make some snapshots? Update tutorial etc.? — The preceding unsigned comment was added by Okias (talk • contribs) 15 October 2013

This is outdated now, we are at E24. Juippis (talk) 12:39, 23 June 2020 (UTC)

Review of live ebuilds (06-oct-2016)

Talk status

This discussion is done.

ebuilds in overlay mentioned in article are broken (neither version of efl is possible to emerge), it seems to me that bar overlay ( https://github.com/tokiclover/bar-overlay ) is the closest to working ebuild. — EvgeniyZh

See also: https://github.com/rafspiny/enlightenment-live/issues/10 Pavlix (talk) 13:15, 6 October 2016 (UTC)

No more separate README.wayland

Talk status

This discussion is done.

There is a link to README.wayland on the page Enlightenment, and it points to 404 error:

Important
Upstream requires systemd to be used when enabling wayland, see Wayland requirements.

I found commit where the file was removed: 7794dc984d701e4749ffb9e4a087294ff592a34d. I see some ways here:

• replace link from README.wayland to README, but then original meaning about systemd will be lost;
• use link to the historic README.wayland, but if something changes in upstream;
• use link to historic README.wayland + change text that it may be not relevant.

--Vazhnov (talk) 09:59, 27 September 2020 (UTC)

Thanks, this is updated now. The infobox is redundant since the dependencies are correctly handled within efl ebuild for a long time now.

I also updated few bits on the page here and there.

Juippis (talk) 06:14, 28 September 2020 (UTC)

EFL recommended USE flags update

Talk status

This discussion is done as of 2024-05-18.

We need an update on the recommended flags for EFL on this page. I would also like to have scenarios as it's not obvious for all if a particular deployment is achievable on either the stable Enlightenment ebuilds or the live ones. For instance I'd like to test Entrance with OpenRC, Elogind on X. The USE flag expressions are fine for trying to figure it out, but whether that's a viable scenario or not isn't obvious without launching the build and going blind on it. Maybe point to upstream documentation if there's any?

Vokiel (talk) 16:22, 19 May 2021 (UTC)

I'm sorry I don't quite understand. You should read the Entrance upstream for requirements, and perhaps write your own ebuild with the requirements coded there. Well, the upstream of revived Entrance do also offer a layout for enlightenment ebuilds, so you might have luck in using that overlay / copying the Entrance ebuild there. It's hard to "advertise" what USE flags are necessary for Entrance in here, as Entrance is not available in the ::gentoo repository.

If you look at the efl ebuild in ::gentoo, it has many + marks in front of some USE flags. Those are the default recommended settings.

For the next efl update, there's a bug to be solved with some of the default USE flags that are causing conflicts in Gentoo. Please see https://bugs.gentoo.org/757339

-- Juippis (talk) 12:05, 7 June 2021 (UTC)

Vokiel I guess this should be closed, then?

— Waldo Lemmer 13:18, 18 May 2024 (UTC)

efl-9999::enlightement-live dependencies

Talk status

This discussion is done.

Encountered 2 issues with the ebuild: First it requires lua 5.2 and portage latest stable version is 5.4.X. I had to add the versions after 5.2 to /etc/portage/package.mask/enlightenment and re-emerge --oneshot. Second it now requires libheif, which should be added to the dependencies on the ebuild. I just emerge --oneshot libheif to make to build pass the configuration stage.

Vokiel (talk) 17:34, 19 May 2021 (UTC)

Build for @enlightement-core-9999::enlightenement-live went through with the following use flags:

• dev-libs/efl-9999::enlightenment-live X bmp connman eet fontconfig gif glib gstreamer harfbuzz ibus ico jpeg2k nls opengl pdf ppm psd pulseaudio sdl sound ssl svg tiff webp xml
• x11-wm/enlightenement-9999::enlightenment-live doc eeze nls pam udev

Vokiel (talk) 17:42, 19 May 2021 (UTC)

Please direct such concerns/bugs to the overlay maintainer. "live" ebuilds have ever changing requirements and will always break when no one is watching. --Grknight (talk) 17:44, 19 May 2021 (UTC)

"Latest Enlightenment" vs. "Stable Enlightenment" Directions Unclear

At first glance, it seems like you get the latest version by running emerge --ask enlightenment while you get the stable version by running emerge --ask x11-wm/enlightenment, but that's not how Emerge works; in both cases, the package installed is x11-wm/enlightenment since you can omit the name of a group as long as there is only one match on package name across all groups.

I believe this could be further clarified by:

1. Making the command under "Latest Enlightenment" be emerge --ask x11-wm/enlightenment so that the correct package is always installed and a Gentoo novice doesn't get the impression that you get the latest version of a package by omitting the group.
2. Indicating that _once you have pinned your build of choice_, you can use the same command as under "Latest Enlightenment" to install just that version.

Alternatively, remove the "Stable Enlightenment" section completely since the process of pinning a version isn't specific in any way to Enlightenment and has its own documentation. --GuyEP (talk) 15:48, 8 June 2024 (UTC)