From owner-freebsd-ports@FreeBSD.ORG Tue Apr 12 11:26:26 2005 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 2AC5516A4CE for ; Tue, 12 Apr 2005 11:26:26 +0000 (GMT) Received: from smtp.xbsd.org (xbsd.org [82.233.2.192]) by mx1.FreeBSD.org (Postfix) with ESMTP id A9AF243D55 for ; Tue, 12 Apr 2005 11:26:25 +0000 (GMT) (envelope-from flz@xbsd.org) Received: from localhost (localhost.xbsd.org [127.0.0.1]) by smtp.xbsd.org (Postfix) with ESMTP id B879B115F2; Tue, 12 Apr 2005 13:30:53 +0200 (CEST) Received: from smtp.xbsd.org ([127.0.0.1]) by localhost (srv1.xbsd.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 27353-08; Tue, 12 Apr 2005 13:30:47 +0200 (CEST) Received: from localhost.localdomain (ALagny-109-1-26-105.w81-49.abo.wanadoo.fr [81.49.53.105]) by smtp.xbsd.org (Postfix) with ESMTP id 21BD211A25; Tue, 12 Apr 2005 13:30:46 +0200 (CEST) From: Florent Thoumie To: George Kouryachy In-Reply-To: References: Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-KAJ+/7Zy82RYZbFqs8qW" Date: Tue, 12 Apr 2005 13:26:17 +0200 Message-Id: <1113305177.764.23.camel@innercity> Mime-Version: 1.0 X-Mailer: Evolution 2.2.1.1 FreeBSD GNOME Team Port X-Virus-Scanned: amavisd-new at xbsd.org cc: Dan Langille cc: freebsd-ports@freebsd.org Subject: Re: Ports version upping policy? X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Apr 2005 11:26:26 -0000 --=-KAJ+/7Zy82RYZbFqs8qW Content-Type: text/plain; charset=iso8859-15 Content-Transfer-Encoding: quoted-printable Le Mardi 12 avril 2005 =E0 15:12 +0400, George Kouryachy a =E9crit : > Hi. >=20 > I've noticed some ports I'm using are too outdated against the upstream > E. g. python Toy Parseg Generatior (tpg) port is still 3.0.0, although > there is 3.0.5 with many bugfixes. >=20 > Another example is tardy (tarball on-the-fly editor). It just ups from > 1.11 to 1.12, but the new version has many changes and meanwhile the > author switched it's website. >=20 > The Q are: > 1. I have stable new-versioned ports edited by myself. Can I push it > to main ports tree instead of rewriting my own one after every cvs > update? You need to have write-access to the ports tree, so for now, that's not (yet) possible. > 2. I wrote a letter to every port maintainer picking their emails > directly from pkg-info, but got no answer. Was there a wrong style of > request? Maybe it's better to write to some maillists or use PR? There > are no patches needed to compile the new ports and there a no "stable" > and "unstable" versions of tardy and tpg, so there seems to be lack of > maintainer's care not the lack of maintainers time... People can be busy with life and not thinking about their ports=20 all the time. Use send-pr to send your patches. Follow the=20 instructions written in the Porter's Handbook. > 3. tardy maintainer is "ports@freebsd.org". Does it mean the port is > unmaintained? Yes, I've asked Dan Langille to add a special notice for these=20 ports so that people know they are unmaintained. Maybe we should think about it again. Dan ? --=20 Florent Thoumie flz@xbsd.org --=-KAJ+/7Zy82RYZbFqs8qW Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQBCW7BZMxEkbVFH3PQRAi0SAJ9c8Gu6Ubzw+Mcv5jZZ/9a5prqnpgCeKjLr l+88VD65P7f9fdjm8TD2JV8= =HzlZ -----END PGP SIGNATURE----- --=-KAJ+/7Zy82RYZbFqs8qW--