Skip to content

feat: Added classic snap packaging#294

Open
kenvandine wants to merge 1 commit intoFrameworkComputer:mainfrom
kenvandine:snap_packaging
Open

feat: Added classic snap packaging#294
kenvandine wants to merge 1 commit intoFrameworkComputer:mainfrom
kenvandine:snap_packaging

Conversation

@kenvandine
Copy link

First pass at creating a classic snap. It's possible this could be done with strict confinement, we would need to do some investigation to see if there are interfaces to everything required.

@JohnAZoidberg
Copy link
Member

Cool I tried it and it can work locally

> snap package
> snap install framework-tool_v0.6.1-20-gabda498ca6_amd64.snap --classic --dangerous
framework-tool v0.6.1-20-gabda498ca6 installed

> sudo framework-tool --uptimeinfo
EC Uptime
  Time since EC Boot:      00h 43m 55s
  AP Resets since EC Boot: 0
  EC Reset Flags
    PowerOn
  Recent AP Resets

"${CRAFT_PART_INSTALL}/share/fish/vendor_completions.d/framework_tool.fish"

apps:
framework-tool:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

that changes the executable name to hyphen instead of underscore?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The snap name/app-name doesn't allow underscores as it means something different to snapd. Snaps can have different versions installed in parallel, and that "instances" are determined with an underscore.

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

Successfully merging this pull request may close these issues.

2 participants