Hello, My package (emacs-vm) was one of the ones that broke with the upgrade to Emacs 28 in F36. I'm trying to get it to work again. One of the issues is that it shows up a large number of warnings. After some time I've now understood this is because of the new native compilation feature. Since my package doesn't include any *.eln files and Emacs will do the compilation on first use, and put in the home directory. The VM package has a lot of old code that triggers warnings. Previously those have only shown up at build time, and I have hoped for upstreams to some day fix them. Now they will also show up at run time, which obviously is a more annoying user experience. That brought up a question: what should Emacs add-on packages do when it comes to native compilation? Should they build and bundle native code? If I understand it correctly, that would mean a new patch build of Emacs itself would also require a rebuild of all add-on packages. Or should we let Emacs recompile native files at run time? That would make the recompilation at Emacs upgrades automatic, but it would on the other hand put a copy of all used libraries in each user's home directory. I checked the packaging guidelines (https://docs.fedoraproject.org/en-US/packaging-guidelines/Emacs/) but it didn't mention anything around this as far as I could tell. (It still talks about xemacs which has been retired from the distribution, which tells me it hasn't been updated very recently.) To make things worse for me, with some updates VM initially works after issuing the warnings, but doesn't work on the second start of Emacs, when it doesn't have to recompile the code. But that's a different story. _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
