Date: Sat, 24 Jul 2010 23:46:09 -0700 From: Rob Farmer <rfarmer@predatorlabs.net> To: jhell <jhell@dataix.net> Cc: FreeBSD Ports <ports@freebsd.org>, python@freebsd.org, perky@freebsd.org Subject: Re: ?? lang/python27 ?? Why is this even here ? Message-ID: <AANLkTimJfKW80MscutYvaZHrhD7ftKRmxMGUP55Pt5_s@mail.gmail.com> In-Reply-To: <4C4BBFB9.4040905@dataix.net> References: <4C4BA653.3000102@dataix.net> <AANLkTinqMatM1z_=hF1AjvtKDnhOFxb4po7baHBOYC=B@mail.gmail.com> <4C4BBFB9.4040905@dataix.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Jul 24, 2010 at 9:38 PM, jhell <jhell@dataix.net> wrote: > On 07/24/2010 23:38, Rob Farmer wrote: >> On Sat, Jul 24, 2010 at 7:49 PM, jhell <jhell@dataix.net> wrote: >>> # New ports collection makefile for: =A0 =A0python26 >>> # Date created: =A0 =A0 =A0 =A0 3 July 2003 >>> # Whom: =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Hye-Shik Chang <perky@FreeBSD.o= rg> >>> # >>> # $FreeBSD: ports/lang/python27/Makefile,v 1.166 2010/05/12 12:13:06 we= n >>> Exp $ >>> >>> PORTNAME=3D =A0 =A0 =A0 python26 >>> PORTVERSION=3D =A0 =A02.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/art= icle.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. > > +=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D+ > | This happened?: =A0 =A0 =A0 2010/05/12 12:13:06 | > | And the date now: =A0 =A0 2010/07/25 00:08:51 | > +=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D+ Sorry - I didn't look at it very closely and assumed you were curious about repocopies, since they aren't mentioned in the Porter's Handbook and I suspect most non-committers don't read the Commiter's Handbook. --=20 Rob Farmer > > 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: =A0 =A0python26 > # Date created: =A0 =A0 =A0 =A0 3 July 2003 > # Whom: =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Hye-Shik Chang <perky@FreeBSD.org= > > > 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: > > =A0 1. Do a force commit on the files of the copied port, stating > repository copy was performed. > > =A0 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. > > > -- > > =A0jhell,v > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTimJfKW80MscutYvaZHrhD7ftKRmxMGUP55Pt5_s>