From owner-freebsd-ports@FreeBSD.ORG Mon Apr 13 09:54:24 2009 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5331C106566B; Mon, 13 Apr 2009 09:54:24 +0000 (UTC) (envelope-from utisoft@googlemail.com) Received: from mail-ew0-f171.google.com (mail-ew0-f171.google.com [209.85.219.171]) by mx1.freebsd.org (Postfix) with ESMTP id 87A3B8FC0C; Mon, 13 Apr 2009 09:54:23 +0000 (UTC) (envelope-from utisoft@googlemail.com) Received: by ewy19 with SMTP id 19so1889964ewy.43 for ; Mon, 13 Apr 2009 02:54:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:received:reply-to:in-reply-to :references:from:date:message-id:subject:to:cc:content-type :content-transfer-encoding; bh=h//HlyIGsxAXVuK4XtXcmvMhn9doZZcGPTRZn9ONNFQ=; b=H1NSM2ym0Z0Vv/pirKsv+zDuktJarS1ODib4/g7U8Cos9+lLolbvHlOKfFZ3LVIvKq nhiAy/UAT96vxMe3TaKya1OfFWdNL68qbVYGq/SUG2CNlaviT8Ez631xepEFgJiUj6cB XoZn+sSI/zER9bmteCQ+HvcWXsJY1lCML14KE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:reply-to:in-reply-to:references:from:date:message-id :subject:to:cc:content-type:content-transfer-encoding; b=ntYmsxs0O2bT30teN5d6Oc4asmr0gBL7WnS1XLo3KjhiOERawxBqc7K6MEP5Q23/Bh I+1z1JjnvhkAkNXZTGx8G9Vb9PJxQdgleRlRv8LQ6zIgMJ2i16vfoOlUPC1eTEHulyV6 Dl742fz7q8uq+fxmpsZiTyK2CAdBmBHlPaa/A= MIME-Version: 1.0 Received: by 10.210.127.13 with SMTP id z13mr5146206ebc.57.1239616462337; Mon, 13 Apr 2009 02:54:22 -0700 (PDT) In-Reply-To: <1239526749.45792.4.camel@main.lerwick.hopto.org> References: <20090412024212.1FC2A1CD0B@mail.droso.net> <1239526749.45792.4.camel@main.lerwick.hopto.org> From: Chris Rees Date: Mon, 13 Apr 2009 10:54:07 +0100 Message-ID: To: Craig Butler Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: portmgr-feedback@freebsd.org, FreeBSD Mailing List Subject: Re: FreeBSD ports which are currently scheduled for deletion X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: utisoft@gmail.com List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Apr 2009 09:54:24 -0000 2009/4/12 Craig Butler : > > > On Sun, 2009-04-12 at 09:41 +0100, Chris Rees wrote: >> 2009/4/12 =A0: >> > As part of an ongoing effort to reduce the number of problems in >> > the FreeBSD ports system, we periodically schedule removal of ports >> > that have been judged to have outlived their usefulness. =A0Often, >> > this is due to a better alternative having become available and/or >> > the cessation of development on the existing port. =A0In some cases, >> > ports are marked for removal because they fail to build and install >> > correctly from their sources, or otherwise fail in operation. >> > >> > The ports, and the reason and date that they have been scheduled >> > for removal, are listed below. =A0If no one has stepped forward before >> > that time to propose a way to fix the problems (such as via a PR), >> > the ports will be deleted. >> > >> > >> > >> > portname: =A0 =A0 =A0 =A0 =A0 audio/rosegarden >> > description: =A0 =A0 =A0 =A0The Rosegarden Editor and Sequencer suite >> > maintainer: =A0 =A0 =A0 =A0 ports@FreeBSD.org >> > deprecated because: tcl82 support is going to be dropped >> > expiration date: =A0 =A02009-04-22 >> > build errors: =A0 =A0 =A0 none. >> > overview: =A0 =A0 =A0 =A0 =A0 http://portsmon.FreeBSD.org/portoverview= .py?category=3Daudio&portname=3Drosegarden >> > >> >> Woah! How do I save this? I'm thinking we could replace this with the >> new version (ironically called 1.7.3 rather than 2.1). >> >> What needs doing? > Update the port following the port handbook, =A0submit pr with your > changes, including change of maintainer over to you if you want it... > > http://www.freebsd.org/doc/en/articles/contributing-ports/article.html > also has a link to the port maintainers handbook. > > If you need a hand just shout. > > Cheers > > Craig B > >> >> Chris >> > > Thanks a lot, I'll bear your offer in mind, Chris --=20 A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail?