From owner-freebsd-python@FreeBSD.ORG Sun Jul 25 04:38:21 2010 Return-Path: Delivered-To: python@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6ABE5106566B; Sun, 25 Jul 2010 04:38:21 +0000 (UTC) (envelope-from jhellenthal@gmail.com) Received: from mail-iw0-f182.google.com (mail-iw0-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id 538128FC15; Sun, 25 Jul 2010 04:38:21 +0000 (UTC) Received: by iwn35 with SMTP id 35so2115243iwn.13 for ; Sat, 24 Jul 2010 21:38:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :x-enigmail-version:openpgp:content-type:content-transfer-encoding; bh=1qPruWXeExiCUrxu5YgFlXxnP03qsxb205tA/SIjbow=; b=S1ezp0xLtaDvfX72qcElU3L49eO3SbxSR7x3pf8Naea+gXUHkEoiklR/cRKNIwdk4t nSs3x+gQ1yEkNVw44SeauAbQvRrnD/61TVxnodGXY3a4a2LEikLIbH3Qa+N24CfFhIvF C/Pcp3/YR8tfoKx1YYI+DOiozRs9EdU1Axm9Y= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:x-enigmail-version:openpgp:content-type :content-transfer-encoding; b=NRadAQ/9EN3wMU217dNqMjDxzSDRu5SDL+F6FBbmE4J04iNoYAT8uQIdJPEIgmofxR VhNNa3ads6YRJsczDtCQZ3+hTisXObN8PqafzQGZt5unVGpKplWjN1IfsXgstz2StwYZ MBN9NZ3v/sC+a8A3tA4ZDIjrPaDfNxke4hDMc= Received: by 10.231.159.204 with SMTP id k12mr6462632ibx.42.1280032700316; Sat, 24 Jul 2010 21:38:20 -0700 (PDT) Received: from centel.dataix.local (adsl-99-181-133-55.dsl.klmzmi.sbcglobal.net [99.181.133.55]) by mx.google.com with ESMTPS id e8sm2097707ibb.8.2010.07.24.21.38.18 (version=SSLv3 cipher=RC4-MD5); Sat, 24 Jul 2010 21:38:19 -0700 (PDT) Sender: "J. Hellenthal" Message-ID: <4C4BBFB9.4040905@dataix.net> Date: Sun, 25 Jul 2010 00:38:17 -0400 From: jhell User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.9.1.11) Gecko/20100722 Thunderbird MIME-Version: 1.0 To: Rob Farmer References: <4C4BA653.3000102@dataix.net> In-Reply-To: X-Enigmail-Version: 1.0.1 OpenPGP: id=89D8547E Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: FreeBSD Ports , python@freebsd.org, perky@freebsd.org Subject: Re: ?? lang/python27 ?? Why is this even here ? X-BeenThere: freebsd-python@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD-specific Python issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Jul 2010 04:38:21 -0000 On 07/24/2010 23:38, Rob Farmer wrote: > On Sat, Jul 24, 2010 at 7:49 PM, jhell wrote: >> # New ports collection makefile for: python26 >> # Date created: 3 July 2003 >> # Whom: Hye-Shik Chang >> # >> # $FreeBSD: ports/lang/python27/Makefile,v 1.166 2010/05/12 12:13:06 wen >> Exp $ >> >> PORTNAME= python26 >> PORTVERSION= 2.6.5 >> > > It's a repocopy - in cases like this, instead of starting a fresh file > at version 1.1, one of the cvs administrators copies the files from > the old port so that the history is maintained. So, the copy happened, > but a committer hasn't actually upgraded the port yet. > > It's discussed in the committers guide: > http://www.freebsd.org/doc/en_US.ISO8859-1/articles/committers-guide/article.html#AEN1391 > No offense but I already know this. I do appreciate the time you took to explain this with the additional link. Thank you. I guess I should have made it more clear. +===========================================+ | This happened?: 2010/05/12 12:13:06 | | And the date now: 2010/07/25 00:08:51 | +===========================================+ This is more than 2 months that nothing has been done with this port. Unless I am wrong and the repo-copy is recent with an old date but I thought that the ident(1) line was/is/should be updated when this happens?. After a repo-copy I would have thought that these lines should have been updated to establish the new port and for whom created it, which would then be re-committed bumping the version to 1.167 and recent date so there is no confusion. # New ports collection makefile for: python26 # Date created: 3 July 2003 # Whom: Hye-Shik Chang A nice part about it is you can switch your ORIGIN to that and be all set for the upgrade. ;) Any way I just wanted to give a heads up for this as it seemed pretty odd as things like this usually happen and get updated all about the same time that a repo-copy happens & this has been in ports that I know of for more than ~1.5 weeks without any sort of update. Regards, PS: These were not followed from the link above. When a port has been repo copied: 1. Do a force commit on the files of the copied port, stating repository copy was performed. 2. Upgrade the copied port to the new version. Remember to change the LATEST_LINK so there are no duplicate ports with the same name. In some rare cases it may be necessary to change the PORTNAME instead of LATEST_LINK, but this should only be done when it is really needed -- e.g. using an existing port as the base for a very similar program with a different name, or upgrading a port to a new upstream version which actually changes the distribution name, like the transition from textproc/libxml to textproc/libxml2. In most cases, changing LATEST_LINK should suffice. -- jhell,v