From owner-cvs-all Tue Aug 29 2: 0:45 2000 Delivered-To: cvs-all@freebsd.org Received: from picalon.gun.de (picalon.gun.de [192.109.159.1]) by hub.freebsd.org (Postfix) with ESMTP id C7A4D37B43C; Tue, 29 Aug 2000 02:00:38 -0700 (PDT) Received: (from uucp@localhost) by picalon.gun.de (8.9.3/8.9.3) id LAA06400; Tue, 29 Aug 2000 11:00:22 +0200 (MET DST) >Received: (from andreas@localhost) by klemm.gtn.com (8.9.3/8.9.3) id KAA67536; Tue, 29 Aug 2000 10:47:04 +0200 (CEST) (envelope-from andreas) Date: Tue, 29 Aug 2000 10:47:04 +0200 From: Andreas Klemm To: Satoshi - Ports Wraith - Asami Cc: Andreas Klemm , obrien@FreeBSD.ORG, Bill Fumerola , cvs-all@FreeBSD.ORG, cvs-committers@FreeBSD.ORG, Andreas Klemm Subject: Re: cvs commit: ports/databases/p5-DBD-Pg Makefile ports/databas Message-ID: <20000829104704.A67208@titan.klemm.gtn.com> References: <20000827202609.A29786@titan.klemm.gtn.com> <20000827152643.U57333@jade.chc-chimes.com> <20000827225820.A37044@titan.klemm.gtn.com> <20000827170553.V57333@jade.chc-chimes.com> <20000827233844.A39318@titan.klemm.gtn.com> <20000828164308.D61755@dragon.nuxi.com> <20000829071108.C57347@titan.klemm.gtn.com> Mime-Version: 1.0 Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: ; from asami@FreeBSD.ORG on Mon, Aug 28, 2000 at 11:54:35PM -0700 X-Operating-System: FreeBSD 4.1-STABLE SMP X-Disclaimer: A free society is one where it is safe to be unpopular Content-Type: text/plain; charset=us-ascii Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Aug 28, 2000 at 11:54:35PM -0700, Satoshi - Ports Wraith - Asami wrote: > Well, you cvs remove'd the port. That, in fact, signed its death > warrant.:] Well, then a question. I trusted in "Attic" here, but since I don't know the exact expire dates ... Are there other suggested methods to "disable" a port before removing completely ? Would it be accepted to remove it from categories Makefile or should we introduce another variable DEAD "will be removed in a few weeks" as a sign for other port maintainers, that they have to update. > After the postgresql port is gone from the repository that way, > copying postgresql7 over will not further damage it or anything. But then you would have 2 times the work of changing the port dependencies. 1. change to postgresql7 because this is the new or 2nd stable 2. and then back to postgresql after postgresql is really dead ? Please remember, there can be weeks between recommended usage of postgresql and switching port dependencies to use the new port AND actually deleting old postgresql port entirely. I think the old behaviour to do repository copies and using the port name + number is the recommended way. It worked for years, is current praxis and everything other is involved with complications or more work. I see no easy solution to emulate something like branches other than the way we already do it since years. -- Andreas Klemm Powered by FreeBSD SMP Songs from our band >>64Bits<<............http://www.apsfilter.org/64bits.html My homepage................................ http://people.FreeBSD.ORG/~andreas Please note: Apsfilter got a NEW HOME................http://www.apsfilter.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message