Prefer "etcd" as the source package name
Bug #1341675 reported by
Mark Shuttleworth
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
golang-etcd (Ubuntu) |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
While we do have a precedent in Python, with python-foo being a common pattern for package names, I think that mainly addresses the case where an existing C library is being wrapped, so python-foo is the Python wrapper for libfoo. In this case, etcd is an application, perhaps "etcd" would be a better name for the package?
Changed in golang-etcd (Ubuntu): | |
status: | New → Won't Fix |
To post a comment you must log in.
Confusingly, there are two upstream etcd packages. This one is the etcd client library, which upstream refers to as go-etcd (https:/ /github. com/coreos/ go-etcd) as well.
The server package (etcd itself) is referred to by upstream as just"etcd" (https:/ /github. com/coreos/ etcd), and I have a separate ITP open for that.
https:/ /bugs.debian. org/cgi- bin/bugreport. cgi?bug= 741065