From owner-freebsd-ports@FreeBSD.ORG Tue Mar 2 15:01:56 2004 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 53A2416A4CE for ; Tue, 2 Mar 2004 15:01:56 -0800 (PST) Received: from hood.oook.cz (hood.oook.cz [212.27.205.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8DDC843D2D for ; Tue, 2 Mar 2004 15:01:55 -0800 (PST) (envelope-from pav@FreeBSD.org) Received: from hood.oook.cz (localhost.oook.cz [127.0.0.1]) by hood.oook.cz (8.12.10/8.12.10) with ESMTP id i22N1s4x019637; Wed, 3 Mar 2004 00:01:54 +0100 (CET) (envelope-from pav@FreeBSD.org) Received: (from pav@localhost) by hood.oook.cz (8.12.10/8.12.10/Submit) id i22N1suA019636; Wed, 3 Mar 2004 00:01:54 +0100 (CET) (envelope-from pav@FreeBSD.org) X-Authentication-Warning: hood.oook.cz: pav set sender to pav@FreeBSD.org using -f From: Pav Lucistnik To: Craig Boston In-Reply-To: <200403021655.22130.craig@yekse.gank.org> References: <200403021655.22130.craig@yekse.gank.org> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-1yrRsDRZalO9k6zjjnXt" Message-Id: <1078268513.35350.10.camel@hood.oook.cz> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.5 Date: Wed, 03 Mar 2004 00:01:54 +0100 cc: freebsd-ports@FreeBSD.org Subject: Re: Advice on dealing with upgraded devel port? X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: pav@FreeBSD.org List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Mar 2004 23:01:56 -0000 --=-1yrRsDRZalO9k6zjjnXt Content-Type: text/plain; charset=iso-8859-2 Content-Transfer-Encoding: quoted-printable V =FAt, 02. 03. 2004 v 23:55, Craig Boston p=ED=B9e: > Hi, I'm a little new at port maintership, and I'd appreciate some tips on= the=20 > best way to handle an upgrade to stable/devel ports. >=20 > The current situation is: >=20 > audio/audacity: contains audacity 1.0.0 release (previous stable versi= on) > audio/audacity-devel: audacity 1.2.0pre3 (development version, was=20 > repocopied from audio/audacity before being changed to 1.2.0) >=20 > Now that 1.2.0 has been formally released, what is the best way to handle= an=20 > upgrade such as this: >=20 > Remove audacity and repocopy the devel version to it before upgrading? No, > Keep the old one around somewhere in case somebody needs it for some odd=20 > reason? that's taken care by cvs automagically, > Or just commit patches to upgrade audacity and remove the devel one=20 > altogether? Yes! This is the way it's usually done. --=20 Pav Lucistnik How will you recognize experienced hacker from beginner? Beginner thinks that kilobyte have 1000 bytes. Experienced hacker thinks one kilometer have 1024 meters. --=-1yrRsDRZalO9k6zjjnXt Content-Type: application/pgp-signature; name=signature.asc Content-Description: Toto je =?iso-8859-2?Q?digit=E1ln=EC?= =?ISO-8859-1?Q?_podepsan=E1?= =?iso-8859-2?Q?_=E8=E1st?= =?ISO-8859-1?Q?_zpr=E1vy?= -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQBARRJhntdYP8FOsoIRAtGJAKCazv6E0HUYQNp4yCt0zvjpwxvxbgCdF28L RbgfAMeQ7tPnYfWxFyG5LPs= =BSbH -----END PGP SIGNATURE----- --=-1yrRsDRZalO9k6zjjnXt--