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

Updated for core22-desktop #103

Open
wants to merge 1 commit into
base: 22-arm64-desktop
Choose a base branch
from

Conversation

kenvandine
Copy link

  • Renamed snap to pi-desktop
  • Increased size to accomodate seeded snaps
  • Match default settings from the pc-desktop gadget
  • Make necessary connections

  * Renamed snap to pi-desktop
  * Increased size to accomodate seeded snaps
  * Match default settings from the pc-desktop gadget
  * Make necessary connections
@@ -7,7 +7,7 @@ volumes:
role: system-seed
filesystem: vfat
type: 0C
size: 1200M
size: 3500M

Choose a reason for hiding this comment

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

If you plan to do things like a remodel from older gadget to this one, using min-size: 1200M would keep partitions compatible and make that possible.

Copy link
Author

Choose a reason for hiding this comment

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

This gadget is published as pi-desktop, which is new. But in the future we may need to consider that if we ever need to grow beyond 3500M.

Copy link
Author

Choose a reason for hiding this comment

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

It's entirely possible that we don't want a snap that's published under a different name in the source tree. The current pi-desktop snap is built/published from another repo under the canonical org. I'd like to hear what others think. Keeping it here in a branch will ease merging fixes/improvements from non-desktop branches.

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