[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Executables in pydl



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Le 15/09/2016 à 16:33, Vincent Prat a écrit :
> Hi,
> 
> I am currently working on packaging pydl, and the build system
> produces some executables using entry points defined in setup.cfg.
> 
> The problem is that for each entry point, two executables are
> produced, one for Python 2, and the other for Python 3, but with
> the same name and location (/usr/bin), thus creating a conflict if
> both packages are installed. I see several possibilities to solve
> the issue: - remove these executables, since users could use
> directly the libraries - rename them (e.g.
> compute_templates-python2 and -python3) - mark the two packages as
> conflicting, but I do not think this is a good idea.
> 
> What is your opinion?
> 
> Cheers, Vincent
> 

Dear Vincent,

The second option looks good. Actually I would tend to use the same
convention as the various python/python2/python3/python2.7/python3.x
symlinks. Alternatively you could think of using the alternatives
system to let the local admin decide which implementation should be
the local default.

However I note that the name of the executable is "compute_template"?
sound quite generic to me...

Regards, Thibaut.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBCAAGBQJX2raVAAoJEJOUU0jg3ChApYQP/1VOqF3s0vv/pIKanKJQNJZf
AZNyeEcZb4c32FWOcuVgTdctQK0iKqNAGmQ4aKHAytm75LO6vVre2EZ4s7BUAwdz
fe89pz2MK7diL73rldGZOaqbRu/kGGMqNtL/+jdhYAZ+WAJbMcYIVfTnvCBIS88W
0MjgIomSMbtJQAKBUMsz4nl/p7x9Ra8uodXSbwpCDd0mFOSZkcQVFvBcU739kaFN
Z/j3VWwmpAIoBgaraso5TK45dqJa68kwgQ3g7supmsPKMQSW4X/GP1q6P8IZj1r/
mVSsU/k7oJr1JDc8LK3KiDuenw/6YKxLmEqmu58i2drp056wpV5GwHWJ36VLXYyY
vUmlw5SAeNUGkSVcPbmri4uONfXMtMgC17YW7mdNfdWBn677tfNMSBF2cflPOA7W
f1D+FkBswlEuYPDdIuKplyulr/wJKKCNmRnNoYJLe4823P+LS3LQ8a5dysp/LwAY
xAPuDBhXP2Ejtpfom6Tj1OpFuemur3SRa957cXGSstdWPeonp2eZ9/G3Kj8A8Z5l
9lRHRTMMjFwpHXVLxMMbVMJaIztw+BHO91Ne5rs8Dp4rGavEImg9dpEUiZ3HBRod
E/x5zN33N+nFYzFKQd3lFu6LIOvNGvu8FiZM8c5vEkJvYQX4IsVZce7I/RUly198
Fd/u4SMmEWzxoITBvyGi
=vQjr
-----END PGP SIGNATURE-----


Reply to: