Skip to content
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

How is this meant to work for classic snaps? #198

Open
Kedstar99 opened this issue Sep 11, 2019 · 0 comments
Open

How is this meant to work for classic snaps? #198

Kedstar99 opened this issue Sep 11, 2019 · 0 comments

Comments

@Kedstar99
Copy link

Whilst working on vscode for hacktoberfest, I noticed that the recommended approach was to add this code into stage.

gnome:
plugin: nil
build-packages:
- software-properties-common
override-pull: |
add-apt-repository -y ppa:ubuntu-desktop/gnome-3-26
apt -y update

That and it requires a specific launcher that gets bundled with the given application.

From what I have read so far, classic snaps are unable to use this repo or it's launchers due to the content interface being unable to connect to gnome plugins for valid security reasons.

https://forum.snapcraft.io/t/enable-content-interface-type-between-classic-confinement-snaps/3780

Is there an elegant solution planned to solve this? The current mechanism prevents classic snaps which requires Gnome software from being upgraded to use core18 or using the newly updated gnome-snaps which I assume have some snap specific fixes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant