From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Artur Malabarba Newsgroups: gmane.emacs.devel Subject: Re: Packaging css-mode for GNU ELPA Date: Sun, 21 Jun 2015 10:44:37 +0100 Message-ID: References: <1434806277.1585.1@smtp.gmail.com> Reply-To: bruce.connor.am@gmail.com NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 X-Trace: ger.gmane.org 1434879889 1283 80.91.229.3 (21 Jun 2015 09:44:49 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 21 Jun 2015 09:44:49 +0000 (UTC) Cc: emacs-devel To: =?UTF-8?Q?Simen_Heggest=C3=B8yl?= Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Jun 21 11:44:48 2015 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1Z6bnw-0005c1-5H for ged-emacs-devel@m.gmane.org; Sun, 21 Jun 2015 11:44:44 +0200 Original-Received: from localhost ([::1]:35684 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Z6bnv-0003yR-KM for ged-emacs-devel@m.gmane.org; Sun, 21 Jun 2015 05:44:43 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:46419) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Z6bns-0003yA-AW for emacs-devel@gnu.org; Sun, 21 Jun 2015 05:44:41 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Z6bnr-0000zR-Ef for emacs-devel@gnu.org; Sun, 21 Jun 2015 05:44:40 -0400 Original-Received: from mail-la0-x22d.google.com ([2a00:1450:4010:c03::22d]:33792) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Z6bnr-0000z3-5U for emacs-devel@gnu.org; Sun, 21 Jun 2015 05:44:39 -0400 Original-Received: by lagx9 with SMTP id x9so6863829lag.1 for ; Sun, 21 Jun 2015 02:44:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:sender:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=u8eyR9bT64R2JTkV9YcvcPjTvCa6XqT+7B1uK9+V4BE=; b=kjlmdsaF1xLRWIMn8ekkVwfCUpbO2znrb9Jz1qX2DMc3piI8uGt2PKGV9fXpHfx+Ax GMTB4OL/7wEjP4o2r2uu2fEElN6aSJ+vY1/2+4yzW9/zDDYDZB1LAgLzWpozW2hzUSyH dNO0F8EJHgEmxjqyKncUESURpxydEYddcCSRPdbdEAyVNFRubv26glbER+45DGMs47p8 wCTgTMdd1FhplVQ5PSnB952m96RABeVDx7lC2yZUXxVMFjuOlOyQ/lhtsrbvmWzCws1K dIaoyscc11kGjQy5RDKjpfu2uutV9za5it8aWUQPwcQ5cH1oAU1rERdlYK6W+L5Qe52U 9yAg== X-Received: by 10.152.7.239 with SMTP id m15mr24497601laa.95.1434879877458; Sun, 21 Jun 2015 02:44:37 -0700 (PDT) Original-Received: by 10.25.214.133 with HTTP; Sun, 21 Jun 2015 02:44:37 -0700 (PDT) In-Reply-To: <1434806277.1585.1@smtp.gmail.com> X-Google-Sender-Auth: Q7sAZn78NjiNYYvv0N9g_2MqLco X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2a00:1450:4010:c03::22d X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:187342 Archived-At: > I think it would be very convenient to be able to subscribe to an ELPA > version of css-mode, which could be updated more frequently than Emacs > releases. I also like to have as many packages on GElpa as possible, but it's important to note the cost of this is not zero. Given that other developers can (and occasionally will) edit the package in one place without knowing to update the other, it can quickly get messy. This would be much cleaner, if someone did that Gelpa-Bootstraping thing Stefan's been asking for. > Is there a procedure for turning a built-in mode into an > ELPA package, and at the same time keeping the built-in package? It > looks like for instance ada-mode is in a similar situation. To be a proper package, it needs to have proper package headers and footers. In the case of css-mode, it's only missing a `Version' header. Once it's a proper package, it's only a matter of dropping it inside the GElpa repo. The biggest issue, as I said, is keeping it updated.