mirror of
https://github.com/debauchee/barrier.git
synced 2026-05-15 14:16:02 -06:00
[GH-ISSUE #688] Create different packages for GUI and non-GUI versions #544
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#544
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?
Originally created by @n0toose on GitHub (May 24, 2020).
Original GitHub issue: https://github.com/debauchee/barrier/issues/688
Barrier's GUI version can be built with the
guibuild flag. That's convenient for operating systems like Gentoo Linux, where I can define whether I want the GUI with every update, but it gets a bit tougher when you need to start instances of Barrier in the background on Debian machines. I think that this would be a useful feature for both myself and other people as well.Therefore, I'd like to request the creation of different packages for the GUI and the non-GUI version of Barrier.
@simons-public commented on GitHub (May 25, 2020):
@AlwaysLivid You can still run barrier without the GUI if the GUI package is installed. The GUI is just a frontend that starts the
barriercclient orbarriersserver processes.@n0toose commented on GitHub (May 25, 2020):
Oh, I understand. I thought that you had to choose between
guiand non-guibuilds-- I tried to look into that myself, up to no avail. Thanks for the response!