Donovan Baarda wrote:
> In my above diagrams the (>=2.1,<2.2) dependancy could be replaced with a
> python-api-2.1 provided by python (as suggested by Neil), but I think this
> actually introduces confusion rather than convenience. The problem is that it
> doesn't really represent a particular v
Quoting Neil Schemenauer <[EMAIL PROTECTED]>:
> Jim Penny wrote:
[...]
> The python is a small package to create a link from /usr/bin/python2.2
> to /usr/bin/python. python-eggs is a dummy package for dependencies
> (similar to what is done for GCC). When we upgrade Python to 2.2 we
> have:
>
>
Jim Penny wrote:
> Why? Could you better explain your reasoning here?
> On the face of it, it certainly seems that python-1.5 ought to be
> able to provide python-api-1.5.
It breaks dependencies. We've been through this before but I'll explain
it again. Here's a dependency graph:
On Tue, Oct 02, 2001 at 06:53:39AM -0700, Neil Schemenauer wrote:
> Carey Evans wrote:
> > 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.
>
> Only "python" can pro
Carey Evans wrote:
> 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.
Only "python" can provide "python-api-*".
Neil
5 matches
Mail list logo
