From owner-cvs-all Mon Oct 29 9:19:44 2001 Delivered-To: cvs-all@freebsd.org Received: from t-mta2.odn.ne.jp (mfep2.odn.ne.jp [143.90.131.180]) by hub.freebsd.org (Postfix) with ESMTP id 6731537B40B; Mon, 29 Oct 2001 09:19:34 -0800 (PST) Received: from artemis.emerald.priv.net ([61.123.75.58]) by t-mta2.odn.ne.jp with ESMTP id <20011029171932755.EAQJ.850.t-mta2.odn.ne.jp@mta2.odn.ne.jp>; Tue, 30 Oct 2001 02:19:32 +0900 Date: Tue, 30 Oct 2001 02:19:47 +0900 (JST) Message-Id: <20011030.021947.88249082.shige@FreeBSD.org> To: ume@mahoroba.org Cc: will@physics.purdue.edu, asami@freebsd.org, jdp@freebsd.org, sf@freebsd.org, cvs-committers@freebsd.org, cvs-all@freebsd.org Subject: Re: cvs commit: ports/editors Makefile ports/editors/emacs21 Makefile distinfo pkg-comment pkg-descr pkg-message pkg-plist ports/editors/emacs21/files patch-configure.in patch-lib-src:Makefile.in patch-man:Makefile.in From: Shigeyuki Fukushima In-Reply-To: <20011030.014335.98951907.ume@mahoroba.org> References: <20011024150015.Q25747@squall.waterspout.com> <20011029.142548.06934931.shige@FreeBSD.org> <20011030.014335.98951907.ume@mahoroba.org> X-Mailer: Mew version 2.0 on Emacs 20.7 / Mule 4.0 (HANANOEN) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG From: Hajimu UMEMOTO Subject: Re: cvs commit: ports/editors Makefile ports/editors/emacs21 Makefile distinfo pkg-comment pkg-descr pkg-message pkg-plist ports/editors/emacs21/files patch-configure.in patch-lib-src:Makefile.in patch-man:Makefile.in Date: Tue, 30 Oct 2001 01:43:35 +0900 (JST) > shige> emacs-21.x port -> editors/emacs-devel > Umm, I don't think that it fits for current status of Emacs21. > emacs-21.1 is now release version. emacs-devel is an bad naming? emacs-current is ok? There is a discussion at ports-jp ML how to maintain ports for two or more version of an software. For example, emacs-19.x, emacs-20.x, emacs-21.x, and more... There is two methods how to do it. Let an distributed software `foo', There is foo-1.x, foo-2.x, and foo-3.x which we want to support by ports/packages system. Method 1(naming with version): In this method, RC is occured always when new version of foo has released. Now, for example, this is applied for editors/emacs. RC RC foo1 ---> foo2 ---> foo3 | | | | UP | UP | UP v v v foo1 foo2 foo3 | | | obsolete <---+ | | obsolete <-----+ | obsolete <-----+ foo1: a port for foo-1.x. foo2: a port for foo-2.x. foo3: a port for foo-3.x. RC: repository copy UP: update commit (revision up) Method 2(-stable/-current or -stable/-devel): In this method, RC is occured only when obsolete version of foo want to save on the ports tree. (In other words, an obsolete version of foo-package is desired to be distributed.) RC foo-stable ---> foo-current (for foo-1.x) (for foo-2.x) | UP | UP v v : : : : | UP | UP RC(*1) v v foo1 <--- foo-stable foo-current (for foo-1.x) (for foo-2.x) | | | | apply a diff | | +<-----------------+ | | UP | UG v v foo-stable foo-current (for foo-2.x) (for foo-3.x) foo1: RC: repository copy UP: update commit (revision up) UG: Upgrade to a new version. *1: only when required. Any other good method?? Thanks. --- shige To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message