-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hooks: Add hook to expose Endless Key launchers in app grid #168
Conversation
It doesn't need to be executable. If you look at the other files in this directory, only the ones ending in |
I agree that it's a little ugly to write a shell script to write an embedded shell script to a place, but for better or for worse that's how it's done for now. You could imagine instead putting the file in the OS, and then just making a symlink here. But I think this is OK. |
ec0d4cc
to
639ccff
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This feels like the kind of thing that should be in the OS. In fact, we already have this exact thing for regular Kolibri.
I threw a test build at Jenkins, and it errored out with:
|
Indeed, another approach here is we change eos-kolibri to also build its own I'm not too bothered by this implementation, but I'm curious if this is going to be needed for a lot of images, or if it's just a one-off? |
https://phabricator.endlessm.com/T35614 Co-authored-by: Will Thompson <[email protected]> Co-authored-by: Dan Nicholson <[email protected]>
9d43966
to
fc341b7
Compare
Is this the right idea? It sort of feels dirty to include a whole shell script here. And do I need to make it executable?
https://phabricator.endlessm.com/T35614