Hi Wouter, thanks for shedding light on the history. And thanks for
discussing this openly!
Assuming there are no additional aspects to the discussion I would
summarize pros and cons of adding eid-mw as a package to Debian as follows:
Pro:
+ A. One less repository to add. Two sides to this: effort for the
sysadmin, but also https://wiki.debian.org/DontBreakDebian.
+ B. The package would be part of the Debian release cycles. The Debian
team would prepare and test distribution releases in advance and the
distribution release itself would be part of the Debian release process.
+ C. The package would b reusable for more distros than today.
Con:
- D. Upstream won't support issues. Not sure if this is really the case.
I may be making this assumption wrongly? And even so, determining
whether an issue is an upstream or a packager issue should not be too
big a concern.
- E. Additional effort from one or more Debian package maintainers.
+/- F. Debian is moving slowly to update urgent upstream package
releases. I'm not putting this in pro nor in the con category: F.1 In
general, new releases are I believe not very urgent. F2. I think with
backports there is a solution for moving too slowly. On the one hand F3.
adding bpo takes additional effort from the sysadmin, but on the other
hand F4. I feel a lot more comfortable adding bpo than adding a third
party repo.
Do you see other aspects? If this is it I'm still inclined to package at
Debian...
Should we bring this bug to the attention of specific other people?
Pieter
