From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: =?utf-8?Q?=C3=93scar_Fuentes?= Newsgroups: gmane.emacs.devel Subject: Re: Making the tarball with bzr data Date: Mon, 30 Nov 2009 23:44:55 +0100 Message-ID: <87vdgr7hug.fsf@telefonica.net> References: <4B140ACF.9090808@gmx.de> <874oob955s.fsf@telefonica.net> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Trace: ger.gmane.org 1259621360 10888 80.91.229.12 (30 Nov 2009 22:49:20 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 30 Nov 2009 22:49:20 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Nov 30 23:49:13 2009 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1NFF3N-0001lw-5Q for ged-emacs-devel@m.gmane.org; Mon, 30 Nov 2009 23:49:09 +0100 Original-Received: from localhost ([127.0.0.1]:41390 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NFF3M-00037r-RX for ged-emacs-devel@m.gmane.org; Mon, 30 Nov 2009 17:49:08 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NFF3H-00037a-5L for emacs-devel@gnu.org; Mon, 30 Nov 2009 17:49:03 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NFF3C-00036q-8m for emacs-devel@gnu.org; Mon, 30 Nov 2009 17:49:02 -0500 Original-Received: from [199.232.76.173] (port=60284 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NFF3C-00036g-36 for emacs-devel@gnu.org; Mon, 30 Nov 2009 17:48:58 -0500 Original-Received: from lo.gmane.org ([80.91.229.12]:38014) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1NFF3B-0004Bz-Ic for emacs-devel@gnu.org; Mon, 30 Nov 2009 17:48:57 -0500 Original-Received: from list by lo.gmane.org with local (Exim 4.50) id 1NFF39-0001fa-3W for emacs-devel@gnu.org; Mon, 30 Nov 2009 23:48:55 +0100 Original-Received: from 238.red-83-37-167.dynamicip.rima-tde.net ([83.37.167.238]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 30 Nov 2009 23:48:55 +0100 Original-Received: from ofv by 238.red-83-37-167.dynamicip.rima-tde.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 30 Nov 2009 23:48:55 +0100 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 48 Original-X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: 238.red-83-37-167.dynamicip.rima-tde.net User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1.50 (gnu/linux) Cancel-Lock: sha1:ghe/dP0oQTr0hARo+qM/iIbgwlE= X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 3) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:118004 Archived-At: Lennart Borgman writes: > Why do I have to copy the files? Why can't this setup be done with the > already existing files? You can do this, but it practice, it can cause a bit of confussion if the files you already have correspond to a different revision than the tip of the bzr branch you download. How would bzr know that those files are not edited but instead belongs to a past revision? > I have put my little elisp library nXhtml at Launchpad so you can > download it with bzr. However a lot of people already have nXhtml > installed, but it was not checked out from Launchpad. It came from a > zip file or similar. > > Now I believed that since bzr is a new modern system it would of > course have thought of that kind of situation. I am a bad manual > reader so I had probably just not understod how to do it... - it is of > course possible to update the files using only bzr. That was my > believe. First: if all your users had the very same version of your library, you could distribute a tarballed .bzr/ directory with the necessary metadata. Expecting this is unrealistic, though. Second: the amount of traffic you save by re-using the source code on the target machine is nil: when the user downloads the metadata, he gets a compressed history of the source code. You could use a lightweight checkout, and this would be a very short download indeed, but then the user would be very constrained on their Bazaar usage, as almost all interesting features of Bazaar are not usable when everything you have at your disposal is a lightweight branch, apart from risking on the problem mentioned above. Third: if you are thinking about Bazaar as a system for distributing your software, I think that pointing potential users to a bzr branch for obtaining a copy of your library you are raising the entry barrier quite a bit, unless your intended audience already knows Bazaar. > Maybe my believe is crazy. Maybe this should not be possible for some > reason. But I do not understand why. It is possible. It is not worthwhile. [snip] -- Óscar