Re: Debian Python policy & Upgrade Path (draft/proposal)
Matthias Klose <doko@cs.tu-berlin.de> writes:
> Carey Evans writes:
>
> > Another possibility is for python-base to go away, and for a new
> > package that conflicts with it, and has a different name, to take its
> > place.
>
> basically that is Neil's proposal of a python-api package.
I thought python-api was mostly copied from Perl, which took several
tries to get right.
But I'm suggesting a smaller change, just replacing all mentions of
'python-base' by (for example) 'python-bin' (cpython? python-main?) in
the policy docs, and repackaging the new python-base as that package.
Surely it's easier to create a package like:
Package: python-bin
Version: 2.1.1-x
Depends: python2.1-base
Conflicts: python-base
than to maintain a huge Conflicts line forever? It should make
dselect and apt faster too.
If you do prefer to go with the Conflicts, we'll need to check whether
there are any Ximian or Progeny packages that need to be included as
well.
--
Carey Evans http://home.clear.net.nz/pages/c.evans/
"Ha ha! Puny receptacle!"
Reply to: