Ganesan Rajagopal writes: > >>>>> Steve Langasek <[EMAIL PROTECTED]> writes: > > >> That much is obvious. The point is wouldn't it be confusing to the user to > >> call the package python-ctypes when it doesn't support the current python > >> version? Oh well, I guess I can put in something in the description to > >> explain this. > > > A package named python-ctypes must support the current python version: it > > must ensure this by having a versioned dependency on the versions of python > > that it is compatible with. > > > That means that if python-ctypes only supports python (<< 2.5), and python > > is at Version: 2.5.0-1, python-ctypes will not be installable (and will need > > to be updated). > > This is exactly my point. There will be no python-ctypes supporting python > >= 2.5. That's why I am arguing that there needs to policy exceptions to > allow a package named python2.4-ctypes. Josselin seems to think different.
I think, the name should be still python-ctypes, with the attributes: Depends: python (>= 2.3), python (<< 2.6) Python-Version: 2.3, 2.4 with the python2.5 package providing python2.5-ctypes. Same thing with other modules, which are included in the python standard library. Matthias -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
