Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upGitHub is where the world builds software
Millions of developers and companies build, ship, and maintain their software on GitHub — the largest and most advanced development platform in the world.
appimaged: Move in all desktop files at once #12
Comments
|
And then run
|
|
I think that parts (or all?) of this logic ("scheduled... for integration") might be implemented in AppImageLauncher. Correct @TheAssassin? If so, could the logic be moved to libappimage so that all libappimage consumers would get to use it? |
|
@probonopd From my point of view The schedule feature implies threading which is a very error prone feature and every developer has a different favorite library to do it. My vote goes to keep such feature out of |
|
@azubieta can you make it work in |
|
Sure, but as you suggested it would be nice to have part of this feature on |
|
Yes, I thought it would be good to abstract that away in
Exactly because of this I would say let's do it once and in a correct way rather than have every developer fight with this on their own, leading to many (different) bugs. |
|
So @azubieta how can we get the situation improved? |
|
What can we do to get this done after all? Instead of duplicating (copying) code from AppImageLauncher, I still think it would be great if |
|
|
(from AppImage/AppImageKit#577)
Currently we are writing desktop files as soon as we have extracted them to
.local/share- this triggers some desktop managers to rebuild the menus after every desktop file, resulting in a major slowdown of the system.So instead, we should extract them to a temp location and only after we are "done" (as in: we did not process any new AppImages in the last second or so), move them in together at once.