Date: Wed, 14 Apr 2004 19:29:03 +0200 (CEST)
From: Alessandro Selli <dhatarattha@route-add.net>
To: gopher@complete.org
Subject: [gopher] Re: pygopherd on Debian stable
In-Reply-To: <20040414140107.GB14612@excelhustler.com>
Message-ID: <Pine.LNX.4.58.0404141922240.11846@tanatos>
References: <Pine.LNX.4.58.0404140939030.9807@tanatos>
 <20040414140107.GB14612@excelhustler.com>
MIME-Version: 1.0
Content-type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Sender: gopher-bounce@complete.org
Errors-to: gopher-bounce@complete.org
Precedence: bulk
Reply-to: gopher@complete.org

Il giorno Wed, 14 Apr 2004, John Goerzen così ha scritto:

|>   	I'm considering installing pygopherd to replace UMN gopherd on a
|>   	Debian stable server running on a SPARCStation5.  However, this
|>   	distribution comes with python version 2.1.3, while pygopherd
|>   	needs version 2.3.  In order to have pygopherd running I'd need
|>   	to upgrade the server to the testing python package, plus a
|>   	small number of other dependencies.  I wished I didn't need to
|
|You have several different options.  You can probably get a usable
|Python for woody from www.backports.org or www.apt-get.org.

  They both carry python2.2 for the Sparc architecture.  Humm...

|However, I have an even easier solution -- you can just install Python
|from source.

  I like this idea.  Yes, I will definitely do this.
  Than you,


  Sandro


-- 
Bellum se ipsum alet
       La guerra nutre se stessa

Livio, "Ab urbe condita", XXXIV,9