i wrote enlightenment_remoVe instead of enlightenment_remoTe
yeah exactly, that's what the user is meant to do from the menus, isn't? mmh... maybe a good thing to ask an extra question to know if wants to logout or shutdown or suspend... ok changed
mmh... no bullseye uses a different directory tree for the hooks, since bullseye is not yet the "official" version of elive none of the hooks on elive-upgrader are included on it, this is for security and reliability purposes of course (each distro has its own line of hooks), -could- be possible in some way to include them but stills a difficult and unreliable thing, for example the hooks are run as:
brainstormed idea...
* if your version of elive is 1.2.3 and there's a hook for 1.2.3.1, this hook is run, same for a next one as 1.2.4 found, but the ones like 1.2.1 are not because they are older than your own elive system (so already included) * different distro will have a different number since it follows a different development thread, bullseye on this case would be 1.2.3 or would be 2.2.3 ? (in your case there's no version, its only the previous 1.2.3 buster system upgraded)On the other hand, stills a problem in a different way: elive-upgrader always requires packages updated, and they are not very updated in bullseye at the moment, so even if elive-upgrader includes the hooks, there's not the packages updated with these new features (will be in a next full bullseye rebuild)
On the other hand, i think it makes sense to :
- if buster is 1.2.3 and there's a buster hook 1.2.3.1, use it
- if bullseye is 1.2.3 (updated from buster) and there's a buster hook 1.2.3.1, use it
- if bullseye is 2.2.3 (an officially new elive version) and there's a buster hook 1.2.3.1, don't use it (its older)
- if bullseye is 2.2.3 (an officially new elive version) and there's a buster hook 1.2.3.2, don't use it (its older)
- if buster is 1.2.3 and there's a bullseye hook 2.2.3.1, don't use it (buster = older than bullseye which means incompatible, should have its own thread)
- buster can have 1.2.4 and 1.2.5 builds, but never 2.2.4 or 2.2.5, so hooks from newer distro should never be run
mmmh... this sounds like a complex feature to implement in a reliable (stable) way i will note it...
I hope to make the switch to bullseye soon!, but i still working on the website (announcement, emails fixing crons, etc..) so probably will happen after that (in any case, the next release should use bullseye)
not heavy so sounds good... i will need to include some "demo files" on the user's home so they can know they can do these things
update: @triantares I installed python-efl in buster and didn't worked (in bullseye does?), not the example of your link and not the examples in /usr/share/doc/python-efl/examples/ from the python-efl-doc package too
note: @triantares can you move the python-efl topic (your 2 comments) to a new thread on Dev ? can be good to have this topic entirely separated for pythonistas
note2: looks like a nice replacement of the ctrl-alt-del tool if you really want to develop / play with it we can open a specific thread about it too, for example it will require to use gettext so that it can be translatable in other languages and the packager should correctly deal with it to include it on eltrans