You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is not really a full issue or bug report, but as an Ubuntu developer, I am acutely aware of the evils of package naming. This is a suggestion on the basis of my experience as a Packager.
The current binaries built for GitHub Desktop for Linux (RCs) are generated so that the package itself in the debian/control files and others is named desktop.
This is extremely ambiguous and unclear what it actually is, and makes understanding what is actually installed or usable or not equally more difficult.
If possible, I would suggest that you adjust the packaging so that the binary for GitHub Desktop is installed as github-desktop, and that the package name be adjusted as well. It currently installs as desktop and that is very ambiguous as to what it actually is.
The text was updated successfully, but these errors were encountered:
teward
changed the title
Debian Packaging: Executable name 'desktop' and package name 'desktop' ambiguous
Debian Packaging: Executable name 'desktop' and package name 'desktop' are ambiguous
Apr 10, 2018
This is not really a full issue or bug report, but as an Ubuntu developer, I am acutely aware of the evils of package naming. This is a suggestion on the basis of my experience as a Packager.
The current binaries built for GitHub Desktop for Linux (RCs) are generated so that the package itself in the
debian/control
files and others is nameddesktop
.This is extremely ambiguous and unclear what it actually is, and makes understanding what is actually installed or usable or not equally more difficult.
If possible, I would suggest that you adjust the packaging so that the binary for GitHub Desktop is installed as
github-desktop
, and that the package name be adjusted as well. It currently installs asdesktop
and that is very ambiguous as to what it actually is.The text was updated successfully, but these errors were encountered: