On Thu, 27 Aug 2020 at 16:31, Sebastian Kuzminsky <seb.kuzmin...@gmail.com> wrote:
> No. Changing the Standards-Version in the control file signals that > your package adheres to the new Standards-Version, so we would need > significant work on our packages in order to do that. > > Here are the changes between Standards-Versions. This is a huge task. > > https://www.debian.org/doc/debian-policy/upgrading-checklist.html I already linked to that page, and the task did not appear that huge. In fact I decided that we probably already comply with 3.9.8, but with questions: Std 3.9.4 section 7.8: I am not clear if "Built Using:" is needed for any package included as a binary, or just for those where no source is included. Std 3.9.6 section 10.1 I don't know how to be sure that we don't statially link in to Gnu C libraries. Std 3.9.6 section 4.4 says that I should use my name in the debian/changelog. I have done this but am concerned that this implies I should also update the "Origin" in the InRelease file to be my name rather than Seb's. But if I do that then the upgrade will fail in synaptic and in apt-get. This caused problems with Google Chrome: https://askubuntu.com/questions/1090676/how-to-update-google-chrome-70-after-change-in-origin-value Std 3.9.8 section 9.6 says that menus should use freedsktop.org standards. We do this for the "CNC" menu, but I am unclear if this also applies to the individual GUIs? If so then that would be a big job. -- atp "A motorcycle is a bicycle with a pandemonium attachment and is designed for the especial use of mechanical geniuses, daredevils and lunatics." — George Fitch, Atlanta Constitution Newspaper, 1912 _______________________________________________ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
