Bug 36589

Summary: www/pyweblib: use current python
Product: Ports & Packages Reporter: Alan E <ports>
Component: Individual Port(s)Assignee: freebsd-ports (Nobody) <ports>
Status: Closed FIXED    
Severity: Affects Only Me CC: oddbjorn
Priority: Normal    
Version: Latest   
Hardware: Any   
OS: Any   
Attachments:
Description Flags
file.diff none

Description Alan E 2002-03-31 21:30:01 UTC 
The www/pyweblib port has an explicit force of
PYTHON_VERSION=python2.1.  The package seems to build and install fine
on current python (2.2_1), and there is no indication on the
software's home page (last updated Feb 2002) of any incompatibility
with 2.2.

This is one of the few (< 5) packages which specifically require 2.1, and
I don't see a reason for that to persist.

Fix: ==8<====8<====8<====8<====8<====8<====8<====8<====8<====8<==
Comment 1 Alan Eldridge 2002-04-02 15:59:18 UTC 
I received the following mail agreeing with the patch from the
maintainer. Since it has his OK, let's apply the patch and close this
PR. Thanks.

From: Oddbjorn Steffensen <oddbjorn@tricknology.org>
To: Alan Eldridge <ports@geeksrus.net>
Subject: Re: www/pyweblib: use current python

On Sun, Mar 31, 2002 at 03:28:05PM -0500, Alan Eldridge wrote:
> The www/pyweblib port has an explicit force of
> PYTHON_VERSION=python2.1.  The package seems to build and install fine
> on current python (2.2_1), and there is no indication on the
> software's home page (last updated Feb 2002) of any incompatibility
> with 2.2.

I did this to avoid a legacy 1.6 installation I had on my machine,
but forgot to correct it prior to submitting the port. Thanks for
spotting it.


> This is one of the few (< 5) packages which specifically require 2.1,
> and I don't see a reason for that to persist.

Agreed.

-oddbjorn

-- 
AlanE
"When the going gets weird, the weird turn pro." - HST
Comment 2 Thomas Gellekum freebsd_committer freebsd_triage 2002-04-11 12:50:35 UTC 
State Changed
From-To: open->closed

Committed, thanks.