* Emilio Pozuelo Monfort , 2010-06-06, 00:41:
Since the Debian Policy forbids packages that don't provide the same
functionality (like these two modules) to conflict with each other, you
cannot go that route.
Strictly speaking, policy you referred to (10.1) applies only to
conflicting binari
> You put the module in some dir and then use a .pth so you can import it
> normally. This will avoid the file conflict, but not the namespace one, and
> I'm
> not sure what would happen if you install both modules, so you better prod
> upstream into renaming it.
> Cheers,
> Emilio
thanks, I wil
On 06/06/10 11:21, PICCA Frédéric-Emmanuel wrote:
>> Since the Debian Policy forbids packages that don't provide the same
>> functionality (like these two modules) to conflict with each other, you
>> cannot
>> go that route. You could probably hack it with .pth so that you don't need a
>> package
> Hi Frédéric,
Hello
> IMHO one of them needs to be renamed, probably the newest one. If the one you
> want to package is only used in the project upstream mentions, renaming that
> one
> would be a good option They can temporarily do something like this:
> try:
>import newname
> except Imp
Hi Frédéric,
On 05/06/10 17:43, PICCA Frédéric-Emmanuel wrote:
> I would like to package this piece of software:
> http://www.tango-controls.org/static/tau/latest/doc/html/index.html
>
> which provides a tau python module.
>
> but the debian python-tau also provides this tau module.
>
> I alrea
5 matches
Mail list logo
