mirror of
https://github.com/debauchee/barrier.git
synced 2026-05-15 14:16:02 -06:00
[PR #360] [MERGED] Fix snapcraft yaml #1610
Labels
No labels
HiDPI
bounty
bsd/freebsd
bsd/openbsd
bug
bug
build-infra
cantfix
critical
doc
duplicate
enhancement
fix-available
from git
from release
good first issue
help wanted
installer/package
invalid
linux
macOS
meta
needs testing
pull-request
query
question
regression
regression
v2.4.0
windows
wontfix
work-in-progress
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/barrier#1610
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
📋 Pull Request Information
Original PR: https://github.com/debauchee/barrier/pull/360
Author: @maxiberta
Created: 7/10/2019
Status: ✅ Merged
Merged: 7/10/2019
Merged by: @AdrianKoshka
Base:
master← Head:fix-snapcraft-yaml📝 Commits (8)
6bab29aUse version from git tag.916138bFix interface plugs.ddc5fbdAdd commands:barrier,barrierc,barriers.3a4626bDrop custom qt5, use distro provided one.05ccc75Update build-packages and stage-packages.93f4de2Add desktop entry with an app icon.9052135Set snap icon and license.cc15f0cUse appstream metadata from flathub.📊 Changes
1 file changed (+53 additions, -74 deletions)
View changed files
📝
snap/snapcraft.yaml(+53 -74)📄 Description
Hi! This should fix issue #301. Includes lots of fixes and improvements, such as:
-devpackages from final snap - reduces snap size from 289MB to 51MB.barrier,barrierc,barriers(with abarrier-kvm.prefix).Btw, is the barrier-kvm snap official? It's currently in very bad shape. And, it should really be named
barrier, so that the main command will be exposed to users asbarrierwith no prefix. I've checked and the namebarrieris already reserved at the Snap Store, although with no published snaps. Is it reserved by you? If not, you can claim it here.Finally, are there plans for a CI pipeline to publish e.g. daily builds of snaps? If not, you could start with https://build.snapcraft.io. For example, I've already set up my fork to be automatically built and published to the edge channel (hopefully temporarily; will drop this fork once there's an official up-to-date snap).
I can happily help if needed :)
Thanks!
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.