Josselin Mouette wrote:
> Le mardi 04 juillet 2006 à 09:25 +0200, Vincent Danjean a écrit :
>> What would be the interest for an application to be present (compiled)
>> several times on the same system ?
>
> This is the whole point of the new policy. It allows for several python
> versions to be i
Le mardi 04 juillet 2006 à 09:25 +0200, Vincent Danjean a écrit :
> What would be the interest for an application to be present (compiled)
> several times on the same system ?
This is the whole point of the new policy. It allows for several python
versions to be installed at once.
> By the way, I
Josselin Mouette wrote:
> I think you should patch the package so that the binary blob is put in
> a .py module that you can import. Then, you can build this .py once for
> each python version, install it in /usr/lib/pythonX.Y/site-packages,
> after which it can be handled by python-support. (It wi
Le sam 1 juillet 2006 00:19, Pierre Habouzit a écrit :
> Le ven 30 juin 2006 21:03, Vincent Danjean a écrit :
> > Hi,
> >
> > I'm converting one of my package (commit-tool) to the new policy.
> > I was thinking it will be easy, but I found several difficulties.
> > I'm able to deal with them so
Le vendredi 30 juin 2006 à 21:03 +0200, Vincent Danjean a écrit :
> I'm converting one of my package (commit-tool) to the new policy.
> I was thinking it will be easy, but I found several difficulties.
> I'm able to deal with them so that I will be conformed to the new
> policy, but I would like
Le ven 30 juin 2006 21:03, Vincent Danjean a écrit :
> Hi,
>
> I'm converting one of my package (commit-tool) to the new policy.
> I was thinking it will be easy, but I found several difficulties.
> I'm able to deal with them so that I will be conformed to the new
> policy, but I would like to
6 matches
Mail list logo
