Hi Thibaut, Thanks for the clarification to you, too.
I'm sorry I misread Ghislain's answer. I interpreted it in the specific context of the commit I had referenced in my first message as an example, which IMO introduces very little additional complexity - although it may seem somewhat complex in the link I've given, due to the representation as a git diff of a patch.
But I understand that it may not even be necessary, as Ubuntu will have Libav10 at the time they pick up the package.
Cheers, Martin El 03/09/14 a les 11:30, Thibaut Paumard ha escrit:
Dear Martin, I think you are over-interpreting what Ghislain wrote. What he said is rather that your package will likely build unmodified on the next release of Ubuntu, if not on the current one, because Ubuntu will also upgrade there version of libav. You don't *have* to go out of your way to ease the downstream work. Likewise, you don't *have* to make any efforts to make it easier to backport your package to older versions of Debian. However, when it is practical, it is good practice to make the adjustments that will make your package compile unmodified on Debian stable and up-to-date derivative distributions. On the other hand you don't want to obfuscate your package just for the sake of backports. If the patch becomes unreadable, your sponsor will give up on checking it. In the end, it's up to you (and your sponsor) to decide the level of complexity you want to allow in your package. Kind regards, Thibaut.
-- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/5406e34e.90...@steghoefer.eu
