I see no reason not to do this but note: 1. Doing so will require us to change the melpa recipe (which currently moves the the contents of lisp/ to the emms toplevel on melpa). If, that is, we want to keep emms on melpa as well as GNU ELPA.
2. Flattening the file structure may make it easier to write a emms-print-metadata-install (since the package install could more closely replicate the tarball install). However, I do know that we are trying to move away from emms-peint-metadata! ---Fran On Sat, 30 May 2020 at 20:54, Yoni Rabkin <[email protected]> wrote: > > Hello all, > > As stated earlier this month, adding Emms to GNU ELPA is a goal for the > big 6.0 release. > > Things are moving forward with the kind help of the Emacs developers, > but it is now obvious that keeping all of Emms' files in the lisp/ > directory is an impediment. There are a number of technical requirements > of both GNU ELPA (which works a bit differently from melpa) and > package.el that combine to make this the case. > > As a consequence, I want to move all of Emms' files from lisp/ to the > top level. This is less tidy than I ideally wish, yet doesn't seem like > a ruinous compromise. > > Does anyone have a reason why we should _not_ move all of the lisp/*.el > files to the top level? If so, why not? > > I'm going to leave this question open until Wednesday the 3rd of June. > > Thanks and have a great weekend. > > -- > "Cut your own wood and it will warm you twice" > >
