Neil Schemenauer <[EMAIL PROTECTED]> writes:
> spam should depend on python not python-2.1.
In my original example, spam embeds libpython2.1.so. It would make
sense for this to mean it depends on python-api-2.1, though this isn't
what the current shlibs file says.
--
Carey Evans ht
Quoting Neil Schemenauer <[EMAIL PROTECTED]>:
> Donovan Baarda wrote:
> > Packages like extension modules _are_ tied to a particular version and
> hence
> > should be in a python-X.Y-foo package that installs into
> /usr/lib/pythonX.Y.
> > There would also be an empty package python-foo that si
Donovan Baarda wrote:
> Packages like extension modules _are_ tied to a particular version and hence
> should be in a python-X.Y-foo package that installs into /usr/lib/pythonX.Y.
> There would also be an empty package python-foo that simply depends on the
> latest python-X.Y-foo and python pack
Carey Evans wrote:
>/> python-2.1 -\
>spam -- > python
>\---> python-eggs ---> python-api-2.1 ---/
spam should depend on python not python-2.1.
Neil
Neil Schemenauer <[EMAIL PROTECTED]> writes:
[...]
> Excellent point. I've updated the policy document to prevent this. The
> python package should provide python-api-X.Y. Module packages should
> depend on python-api-X.Y. If someone packages an older version of
> Python they should call it p
Quoting Neil Schemenauer <[EMAIL PROTECTED]>:
[...]
I've done some digging in the archives and found things that look surprisingly
like "my proposal" proposed by others. I don't think the finer points of how it
would work were pinned down though, so I'm going to persist untill someone
tells me
6 matches
Mail list logo
