Hello Andreas, > I'd leave it to your opinion whether you think there is a chance for > really confusing the packages or whether an additional hint might add > confusion. May be README.Debian would be a less noisy place to mention > this.
Thanks again for your feedback and tips, they are most welcome. After taking another look at the situation, I am fairly confident that the risk of conflicts should indeed be minimal, and opted for the README.Debian route. The latest version of the package on mentors and the preliminary VCS has been updated. My only minor doubt comes from the fact that the upstream DNA jellyfish package seems to provide binding to several languages [1], Python being among them. It seems the bindings are currently not being included in Debian as an individual package, but I'm wondering if it would be advisable to preemptively reserve the "python-jellyfish" name for them, just in case they are included in the future. Again, thanks for your comments, and I'd be happy to make any further changes if needed! [1] https://github.com/gmarcais/Jellyfish/tree/develop#binding-to-script-languages -- Diego M. Rodriguez 36B3 42A9 9F2F 2CFB F79B FF9B B6C4 B901 06BC E232
signature.asc
Description: Digital signature
