Hi Paul, Paul Wise <pabs@debian.org> writes: > On Mon, 2023-12-04 at 02:28 -0800, Xiyue Deng wrote: > >> I think dh_auto_clean is the right place, because the build failure is >> because that the clean target requires the existence of >> scala-mode-pkg.el, which is generated by Cask. As we don't have Cask, >> we need to provide this before dh_auto_clean runs. > > I think it is against ftp-master rules to have generated files > present that can't be built using only tools from Debian main. > > So I think you would need to package Cask first? Cask and similar tools like Eask and Eldev are tools that automatically install dependencies of an Emacs addon package, which doesn't use and circumvents the system package management. I think the Emacsen team chooses not to package those tools and prefers using dh-elpa for the job, and may override build target to avoid using those tools. See also [1] and [2] for some previous discussions. [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837922#15 [2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875722#16 -- Xiyue Deng
Attachment:
signature.asc
Description: PGP signature