Proposal for transition--FRD
Hi, from the thread I started, I propose we try this: 1) Every package that depend on python checks if it works with python 2.1. 2) We upload python-base v. 2.1, and most of the packages will have to make a new upload (depend on python-base (=2.1 2.2) if anything installed in .../python2.1/). 3) If any package fail 1), we create python1.5-base, and that package will be built accordingly. 4) Everyone be happy with the clean package namespace. 5) This propably mean all packages that depend on python-base (1.6) -- which shoud be any with files in .../python1.5/ -- will have to go into testing at the same time. Will this cause a problem? 6) All packages with files in .../python1.5/ without versioned depends get a critical bug. 7) Contemplate the posibility to install modules in /usr/lib/python-modules/, i.e. a version independent place. (I remember the python people have some objection, but forgot which.) 8) Flame me for writing long task lists. /Micce -- Mikael Hedin, MSc +46 (0)980 79176 Swedish Institute of Space Physics +46 (0)8 344979 (home) Box 812, S-981 28 KIRUNA, Sweden+46 (0)70 5891533 (mobile) [gpg key fingerprint = 387F A8DB DC2A 50E3 FE26 30C4 5793 29D3 C01B 2A22]
Re: Proposal for transition--FRD
Mikael Hedin [EMAIL PROTECTED] writes: [...] 6) All packages with files in .../python1.5/ without versioned depends get a critical bug. Unfortunately, this leaves someone's system broken if they just install some Python packages, and leave the packages that currently depend on python-base ( 1.5.2) installed. The best solution to this is to get rid of python-base, and have all packages depend on python-base-x.y or similar. Packages only get into testing once their dependencies are consistent, and apt-get upgrade won't allow broken dependencies either, so this doesn't really cause much hardship. -- Carey Evans http://home.clear.net.nz/pages/c.evans/ You think you know... what's to come... what you are.
Re: Proposal for transition--FRD
Carey Evans [EMAIL PROTECTED] writes: Mikael Hedin [EMAIL PROTECTED] writes: [...] 6) All packages with files in .../python1.5/ without versioned depends get a critical bug. Unfortunately, this leaves someone's system broken if they just install some Python packages, and leave the packages that currently depend on python-base ( 1.5.2) installed. The best solution to this is to get rid of python-base, and have all packages depend on python-base-x.y or similar. Packages only get into Why not the exciting name python? And confilcts with python-base? Then all the module that depend on python-base (xxx) to be either upgrader or removed. Am I right? It's really strange that we have no python package now, try 'dpkg -p python'. /Micce -- Mikael Hedin, MSc +46 (0)980 79176 Swedish Institute of Space Physics +46 (0)8 344979 (home) Box 812, S-981 28 KIRUNA, Sweden+46 (0)70 5891533 (mobile) [gpg key fingerprint = 387F A8DB DC2A 50E3 FE26 30C4 5793 29D3 C01B 2A22]
Re: Proposal for transition--FRD
Mikael Hedin [EMAIL PROTECTED] writes: [...] Why not the exciting name python? And confilcts with python-base? Then all the module that depend on python-base (xxx) to be either upgrader or removed. Am I right? There's quite a few packages that depend on python, which is a virtual package, and it looks like it used to be a real package. Try apt-cache showpkg python. -- Carey Evans http://home.clear.net.nz/pages/c.evans/ You think you know... what's to come... what you are.
