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: Supporting multiline Package-Requires header Date: Sun, 23 Aug 2015 18:16:39 -0400 Message-ID: References: <87si7rjqmp.fsf@newcastle.ac.uk> <87fv3rjogj.fsf@newcastle.ac.uk> <87fv3po7ss.fsf@russet.org.uk> <87lhd2h5ug.fsf@Rainer.invalid> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1440368880 12509 80.91.229.3 (23 Aug 2015 22:28:00 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 23 Aug 2015 22:28:00 +0000 (UTC) Cc: emacs-devel@gnu.org To: Achim Gratz Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Aug 24 00:27:52 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 1ZTdk0-0004rW-7m for ged-emacs-devel@m.gmane.org; Mon, 24 Aug 2015 00:27:52 +0200 Original-Received: from localhost ([::1]:39891 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZTdZe-0000aE-Jm for ged-emacs-devel@m.gmane.org; Sun, 23 Aug 2015 18:17:10 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:59110) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZTdZG-0000X5-8J for emacs-devel@gnu.org; Sun, 23 Aug 2015 18:16:46 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZTdZB-0001LI-84 for emacs-devel@gnu.org; Sun, 23 Aug 2015 18:16:46 -0400 Original-Received: from ironport2-out.teksavvy.com ([206.248.154.181]:59428) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZTdZA-0001LE-R8 for emacs-devel@gnu.org; Sun, 23 Aug 2015 18:16:40 -0400 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: A0AzFgA731xV/5P+d0tcgxCEAoVVu0CHSwQCAoE8OhMBAQEBAQEBgQpBBYNdAQEDAVYjBQsLDiYSFBgNJC6ICQjPIwEBAQcCAR+LOoUFB4QtAQSZbgWFJJIUghSBRSOCChyBbiKCeAEBAQ X-IPAS-Result: A0AzFgA731xV/5P+d0tcgxCEAoVVu0CHSwQCAoE8OhMBAQEBAQEBgQpBBYNdAQEDAVYjBQsLDiYSFBgNJC6ICQjPIwEBAQcCAR+LOoUFB4QtAQSZbgWFJJIUghSBRSOCChyBbiKCeAEBAQ X-IronPort-AV: E=Sophos;i="5.13,465,1427774400"; d="scan'208";a="161135182" Original-Received: from 75-119-254-147.dsl.teksavvy.com (HELO fmsmemgm.homelinux.net) ([75.119.254.147]) by ironport2-out.teksavvy.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 23 Aug 2015 18:16:40 -0400 Original-Received: by fmsmemgm.homelinux.net (Postfix, from userid 20848) id 3092FAE068; Sun, 23 Aug 2015 18:16:39 -0400 (EDT) In-Reply-To: <87lhd2h5ug.fsf@Rainer.invalid> (Achim Gratz's message of "Sun, 23 Aug 2015 08:33:11 +0200") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.0.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:189089 Archived-At: > The easy solution is to recognize that you already got a complete > package archive from the Org guys which is ready to be deployed. Yes, that is also a problem. But I'd rather we try and solve one problem at a time. > No, it's actually your expectation to have version numbers in the > comments of a non-generated, version-controlled file that's a latent > problem. Keeping that up-to-date would require a stream of otherwise > useless commits in the VCS and result in merge conflicts while keeping > the maint and master branch in sync. Why? We're talking about the org.el that's in the tarball you send us. It doesn't have to be identical to the org.el in your VCS. This said, it could also be identical to the one in your VCS without needing an extra commit: just make sure the version is changed as part of the last commit (since it's the last commit before a new release, it's not completely extravagant to expect that you'd often/usually know this commit will be used for a release and hence needs a change in the org.el's Version: header). Stefan