In article <[EMAIL PROTECTED]> you wrote: > [-- text/plain, encoding quoted-printable, 32 lines --] > > 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?
I'm not sure I follow this either. Are all packages that currently depend on python-base supposed to now depend on python-base <<1.6, and all packages that depend on python2-base now to depend on python2-base>=2.0? It seems to me (with the most horrible command line in the world -- se below) that no packages at all depend on python-base like this... Command line: [EMAIL PROTECTED] ~]$ grep-available -FDepends python-base -sPackage,Depends|less | python -c "import sys,string;l=sys.stdin.readlines();p=filter(lambda i:i[:9]=='Package: ',l);p=map(string.strip,p);p=map(lambda z:z[9:],p);d=filter(lambda i:i[:9]=='Depends: ',l);d=map(lambda j:j[9:],d);d=map(lambda k:string.split(k,','),d);d=map(lambda n:map(string.strip,n),d);d=map(lambda p:filter(lambda q: q[:11]=='python-base',p),d);d=map(lambda r:r[0],d);f=map(None,p,d);f=map(lambda s:string.join(s,': '),f);f=string.join(f,'\012');print f" | sort (recombine onto one line). I bet there's a more efficient way to do this, but grep-dctrl is black magic in parts afaics... Aq. -- S: That must be due to the rather odd way they spelt Aquarius on it. :) Aq: <pet rant>What, you mean sticking an extra 'o' in it somewhere?</pet rant> S: Yes, I can see how that would be upsetting. Actually, it makes you sound Italian. Aquariuso. :) -- Sarabian and I, afe