[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Python policy (was Re: Experimental Python 2.1 packages, release plans)



On Thu, May 24, 2001 at 04:34:35PM +0200, Gregor Hoffleit wrote:
 
> Anyway, while I'm away, perhaps someone could start to audit the packages
> that depend on Python, and file bugs for all packages that don't have a
> correct, explicit versioned dependency on python-base like
> 
>   Depends: python-base (>= 1.5), python-base (<< 1.6)
> 
> or  
> 
>   Depends: python2-base (>= 2.0), python2-base (<< 2.1)
> 

Hmmm....

is the implication of this that every package will still need to be
customised to know which /usr/lib/python-XXX to use?  Is this the
approach that maintainers are taking?

If so, would it not perhaps make more sense to have python packages
detect the version of /usr/bin/python at build time, and adjust
themselves accordingly?

The only problem would be the need for a shlibdeps equivalent or
whatever....

-- 
Peter Eckersley                         http://www.cs.mu.oz.au/~pde 
(pde@cs.mu.oz.au)              TLI:  http://www.computerbank.org.au
<~~~~.sig temporarily conservative pending divine intervention~~~~>
GPG fingerprint: 30BF 6A78 2013 DCFA 5985  E255 9D31 4A9A 7574 65BC

Attachment: pgpWxtGaVO96_.pgp
Description: PGP signature


Reply to: