❦ 2 juin 2020 09:11 +03, Alexandru Ardelean: > Thanks for the message. > I'm still interested in getting this into Debian. > I'd probably need to organize a bit, and ping some co-maintainers. > Maybe also some polish to the debian rules [for packaging]. > But, let's see. > > I'll try to make things as-easy-as-possible for the Debian part.
There is no need to be try too hard. Here are a few steps: - move Debian packaging in a dedicated branch (it needs to be able to evolve independantly of the upstream sources, it's possible to add instructions for user to still be able to use this branch with the code from master). See <https://github.com/Exa-Networks/exabgp/tree/master/debian> for an example (these instructions could be updated as it is now simpler). An alternative would be to do the official packaging on salsa.debian.org using traditional tools (notably, the released tarballs). This way, the upstream repository is kept as is, including the debian/ directory. That's what I do for my own projects (but I am unsure if I would do the same today). - update a bit the packaging (update to a more recent debhelper, remove the prerm hook in favor of a systemd unit) - the --libexecdir=/lib is problematic. Moreover the utils are all arch-independent, so they should be in /usr/share/mstpctl-utils. We can work on that in a pull request after we settle on the first point. -- Instrument your programs. Measure before making "efficiency" changes. - The Elements of Programming Style (Kernighan & Plauger)
signature.asc
Description: PGP signature
