From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: GNU ELPA; mw 0.1: modular MediaWiki interface for Emacs Date: Wed, 15 Oct 2014 13:51:01 -0400 Message-ID: References: <87oatpkof7.fsf@passepartout.tim-landscheidt.de> <87r3ye3mf7.fsf@violet.siamics.net> <87zjd1zj0q.fsf@violet.siamics.net> <87k342zabt.fsf@violet.siamics.net> <87zjcxy6eh.fsf_-_@violet.siamics.net> <87y4shsbf4.fsf@ferrier.me.uk> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Trace: ger.gmane.org 1413395503 31909 80.91.229.3 (15 Oct 2014 17:51:43 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 15 Oct 2014 17:51:43 +0000 (UTC) Cc: Nic Ferrier , emacs-devel@gnu.org To: Ivan Shmakov Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Oct 15 19:51:36 2014 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 1XeSjW-00018K-L0 for ged-emacs-devel@m.gmane.org; Wed, 15 Oct 2014 19:51:34 +0200 Original-Received: from localhost ([::1]:46005 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XeSjW-0007NM-Bp for ged-emacs-devel@m.gmane.org; Wed, 15 Oct 2014 13:51:34 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:54898) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XeSj8-0007JL-MZ for emacs-devel@gnu.org; Wed, 15 Oct 2014 13:51:18 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XeSj1-0000gz-6Z for emacs-devel@gnu.org; Wed, 15 Oct 2014 13:51:10 -0400 Original-Received: from ironport2-out.teksavvy.com ([206.248.154.181]:48765) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XeSj1-0000gs-2x for emacs-devel@gnu.org; Wed, 15 Oct 2014 13:51:03 -0400 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ArYGAIDvNVNFxKjo/2dsb2JhbABZgwaDSlK/a4EXF3SCJQEBAQECASMzIwULCxoCGA4CAhQYDSSIBAivG6J+F4EpjQhJB4JvgUkEqRmBaoNMIYEt X-IPAS-Result: ArYGAIDvNVNFxKjo/2dsb2JhbABZgwaDSlK/a4EXF3SCJQEBAQECASMzIwULCxoCGA4CAhQYDSSIBAivG6J+F4EpjQhJB4JvgUkEqRmBaoNMIYEt X-IronPort-AV: E=Sophos;i="4.97,753,1389762000"; d="scan'208";a="94281912" Original-Received: from 69-196-168-232.dsl.teksavvy.com (HELO pastel.home) ([69.196.168.232]) by ironport2-out.teksavvy.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 15 Oct 2014 13:51:02 -0400 Original-Received: by pastel.home (Postfix, from userid 20848) id AFEF17CFB; Wed, 15 Oct 2014 13:51:01 -0400 (EDT) In-Reply-To: <87y4shsbf4.fsf@ferrier.me.uk> (Nic Ferrier's message of "Wed, 15 Oct 2014 14:35:43 +0100") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.4.50 (gnu/linux) X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 206.248.154.181 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:175427 Archived-At: >> Speaking of the GNU=C2=A0ELPA Git repository, =E2=80=93 it seems to be a >> monolithic one (that is: no submodules are used.) You get to choose (we call the two options "subtree" and "external"). Auctex, rudel, w3, and a few more are installed as "externals", i.e. similar to Git submodules (tho hand-managed). The "external" ones are stored as branches in the same repository (e.g. the externals/auctex branch). >> Curiously, is there a BCP on maintaining a package in a separate >> repository /and/ keeping its history mirrored in the GNU=C2=A0ELPA one? You can host a mirror elsewhere if you want. But the elpa repository is not read-only, so you'll need to pay attention to commits performed there to keep the two trees in sync. >> (FWIW, I=E2=80=99d certainly prefer having a repository of my own to >> keep the history of the MW package alone.) If you install your package as an "external", then the history is of course kept separate. > I offered marmalade's code base for managing the elpa repository. > It's an upload based system, you just push packages in it. > The code is GPLed so there's no concerns there. > Stefan didn't understand what I meant at the time. Hopefully he does > now. Now I understand you suggest we use Marmalade's scripts to manage the GNU ELPA archive, but I still don't know what that means concretely. The fact that we have a local storage of the source and VCS history (with write access so that any Emacs maintainer can install fixes) is an important design choice. Would that easily fit into Marmalade's code base? How does Marmalade track commits to send them back to the respective package's maintainer? Stefan