Date: Wed, 10 Apr 2002 12:31:51 -0400 From: Alan E <alane@geeksrus.net> To: "Karsten W. Rohrbach" <karsten@rohrbach.de> Cc: Alan E <alane@geeksrus.net>, tg@FreeBSD.ORG, freebsd-ports@FreeBSD.ORG Subject: Re: [PATCH] port: python-2.1.2 -> 2.1.3 Message-ID: <20020410163151.GA82892@wwweasel.geeksrus.net> In-Reply-To: <20020410180818.E79746@mail.webmonster.de> References: <20020409194743.A42693@mail.webmonster.de> <20020410165222.B79746@mail.webmonster.de> <200204101153.04522.alane@geeksrus.net> <20020410180818.E79746@mail.webmonster.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Apr 10, 2002 at 06:08:18PM +0200, Karsten W. Rohrbach wrote: >Alan E(alane@geeksrus.net)@2002.04.10 11:53:04 +0000: >> On Wednesday 10 April 2002 10:52, Karsten W. Rohrbach wrote: >> > in followup to my last mail including the make changes as files, here is >> > a patch against the ports tree as of today, 15:40 CEST. it applies from >> > /usr/ports and updates bsd.python.mk, python21 and py-tkinter to the >> > 2.1.3 python bugfix version. >> >> FYI I have an open PR (36353) against Python 2.1, and whichever patch goes in >> first will invalidate the other (for Makefile only). It's not a big deal (my >> patch bumps PORTREVISION, you bump PORTVERSION). > >this should be resolved first, then. it is just a "works for me[tm]" >fix, since i am neither a make or ports subsystem guru. since zope had >severe problems on my freebsd box i needed to fire up py2.1.3 very >quick. i don't want to have zope going down 8 times a day on a >production system. 0. I don't care which one goes in first, as long as they both go in. IMO neither one has any inherent priority. However, yours won't go in as long as there isn't a PR for it. Would you like me make one and submit it for you? 1. I just rechecked, and I didn't even bump PORTREVISION, so there won't be a patch conflict. I raised a false alarm. Sorry. 2. PORTREVISION is the change-counter for the port itself. Has nothing to do with the source-package's version. 3. My patches don't affect Zope. >btw, what about having a post-install telling the user to ln -s his >preferred version of python in /usr/local/bin on his own? i think this >would make sense, because it's quite dangerous if /usr/local/bin/python >gets replaced automagically. The current version of python should own the /usr/local/bin/python binary. Zope is the only other package that actually needs python21. I agree regarding the danger; that's why I'm patching the old versions of python to not do that. -- AlanE "I wanna be sedated." -- The Ramones To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020410163151.GA82892>