Hi, >> I have almost finished preparing emacs-snapshot[0] and as I said to >> Rob, my plan is to keep emacs-snapshot package as close as possible >> to emacsXY package. I know that you've been working on unversioning >> emacs package (BTW Where is that repository?). > > How many of the existing add-on packages in sid have you tested with > your emacs-snapshot package? Do you have some plan to prevent/manage > breakage of add-ons by a new upload of emacs-snapshot? It seems like > every upload is potentially like a library transition, in that changes > in emacs tend to break add-on packages. I use it myself on a daily basis for a few months (and Dima for much longer so he may know more than me about that) with around 20 add-ons. Except the fact that old-style backquotes have been removed for which I have a few patches ready (and which is something that will have to be deal for emacs26 anyway AFAIK), I have not had any problem so far. Anyhow, emacs-snapshot will only be available in sid/experimental and, except 4 source packages, all of them don't Build-Depends on emacs-snapshot. Also, most of the time, add-ons breakage to expect are on deprecated/removed interfaces (such as old-style backquotes) which is something that will have to be dealt anyway on new Emacs stable releases. But I get your point and indeed there need to be a plan to check before each upload of emacs-snapshot whether it breaks add-ons. A shell script installing in a clean chroot emacs-snapshot to be uploaded and all available add-ons in the archive would probably be enough and fairly easy to write? Cheers, -- Arnaud Fontaine
Attachment:
signature.asc
Description: PGP signature