-
Notifications
You must be signed in to change notification settings - Fork 70
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
debian packaging question #3
Comments
Follow-up: I know about the "official" package mentioned here... ...but there are quite a few policy violations on that one:
For instance, we don't generally allow packages to install things under |
Hi realtime-neil@, Thank you for reporting the issue with debian paths. Session Manager service teams will evaluate the request and update here. Thanks, |
The file paths are pretty egregious for packaged software. But also the package name ("session-manager-plugin") is so generic that you don't really know what it's for. The package could also use a better description; "see our website for details" isn't a description of software. And it's a plugin for AWS CLI, but it doesn't even list AWS CLI as a package dependency. It also lists docs like LICENSE and README.md as "conffiles". |
With the creation of #30 , I would call this isuse a proper subset of that one. |
so... where's that update? can't imagine it's taken almost a year to evaluate? |
Update to go 1.16 to support arm64
Another question is why does the package require a service |
For the same reason everything else is this repository looks like this: Because Amazon. For lack of any official response (either in the past or likely forthcoming) I'll make a valiant guess: If Amazon can get you to run their program as |
Is/are the maintainer(s) interested in making this project into a native Debian package? Asking because I use session-manager-plugin on Debian and Ubuntu.
The text was updated successfully, but these errors were encountered: