From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alex Kost Subject: Re: Emacs-Guix released outside from Guix Date: Sat, 17 Dec 2016 11:38:13 +0300 Message-ID: <87bmwbvtl6.fsf@gmail.com> References: <20161215144849.2990-1-alezost@gmail.com> <871sx9atdh.fsf@gnu.org> <87eg18k8td.fsf@elephly.net> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:54248) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cIAVS-0005fH-QB for guix-devel@gnu.org; Sat, 17 Dec 2016 03:38:16 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cIAVP-0007up-MK for guix-devel@gnu.org; Sat, 17 Dec 2016 03:38:14 -0500 List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Ricardo Wurmus Cc: guix-devel@gnu.org Ricardo Wurmus (2016-12-16 01:37 +0100) wrote: > Hi Alex, > > Ludovic Court=C3=A8s writes: > >> Alex Kost skribis: >> >>> Hello, I've been working on Emacs interface outside from the Guix repo >>> for some time, I mean I'm not going to maintain it inside Guix, sorry := -( >>> >>> The main reason, is, well, inconvenience for me: I don't like to bother >>> people with patches, etc. I tried to explain it at >>> . >> >> As someone who=E2=80=99s always trusted you to do the right thing, I=E2= =80=99m of course >> disappointed that we Guix folks didn=E2=80=99t get notified nor consulte= d before >> the fact. I would also have loved a reply to my message back then=C2=B9. >> That=E2=80=99s your choice though. >> >> =C2=B9 https://lists.gnu.org/archive/html/guix-devel/2016-07/msg01110.ht= ml > > First of all, let me tell you that I really appreciate your work on > guix.el! It=E2=80=99s excellent and makes me feel even more at home in E= macs. > > I whole-heartedly second what Ludo wrote and just now and back then: > > It would be a great loss and a technical hindrance if guix.el was mov= ed > out of Guix. I don=E2=80=99t want that to happen, so let me know wha= t the > ransom should be! ;-) There shouldn't be any ransom! I just didn't feel I had enough freedom when I was working on it inside Guix. > We=E2=80=99d love for guix.el to stay. You can already modify the code a= s you > deem appropriate without having to worry about a veto from any of us. Sorry, but I have already pushed too much effort making it a separate project, and it has changed quite a lot comparing to what we have in a Guix repo. >> Breakage will occasionally occur as the Guix APIs change, which will >> make us all a bit sad. What are your thoughts? > > This is the biggie for me. Having the Emacs interface so closely > integrated with the rest of Guix ensured that we wouldn=E2=80=99t have to= worry > about breakage. How could we be ensured? When a breakage happened in the past, an according fix had to be done in the guix repo, and it wasn't available for users until updating 'guix-devel' package. Now when a breakage will happen, an according fix will be done in the emacs-guix repo, and it will be available for MELPA/Quelpa users right away. > In my opinion this move increases the friction for the > users that most care about guix.el for the dubious improvement of > offering a slimmer guix.el to people who =E2=80=A6 don=E2=80=99t use Guix. People can use Guix, but they can still prefer to install Emacs packages via elpa, not via Guix. >> I=E2=80=99ll let you take care of the actual removal, along with update = to the >> Texinfo cross-references and doc/htmlxref.cnf (assuming the manual will >> be available on-line.) I think it would help users to keep >> cross-references between the two manuals. >> >> We need to see what Ricardo thinks and whether or not this can be done >> before 0.12, which is slated for sometime next week. > > Yes, I=E2=80=99ll start preparing for the release (going through the moti= ons) on > the weekend, so that the actual tagging and uploading can happen on the > 20th (busy on the 19th) if all goes well. > > If you go through with the move please double check that the Guix > sources are in a state that=E2=80=99s ready for release. It would be ter= rible > to have a botched release. (Frankly, I=E2=80=99m a little uncomfortable = about > such a big change right before the release, but maybe I=E2=80=99m just be= ing > nervous about doing the release myself this time=E2=80=A6) I'm going to send "removal" patches after the release. BTW thank you for taking care of the release! --=20 Alex