[MacPorts] #36022: kiwi: change to py-kiwi, add python 2.7 support, update to 1.9.29 (was: unification of kiwi port: py*-kiwi)

[MacPorts]

#36022: kiwi: change to py-kiwi, add python 2.7 support, update to 1.9.29
------------------------------------------+---------------------------------
 Reporter:  alexander.afanasyev@…         |       Owner:  macports-tickets@…                   
     Type:  update                        |      Status:  new                                  
 Priority:  Normal                        |   Milestone:                                       
Component:  ports                         |     Version:  2.1.2                                
 Keywords:  haspatch                      |        Port:  kiwi                                 
------------------------------------------+---------------------------------
Changes (by ryandesign@…):

 * cc: ryandesign@… (added)
  * keywords:  => haspatch
  * type:  enhancement => update


Comment:

 The kiwi port was initially committed in 2004. In 2009 (#22124) and 2010
 (#24093) it was suggested to change this to py-kiwi (alright: py26-kiwi;
 we didn't have unified ports back then) and I didn't because I assumed the
 developer who initially committed kiwi had a reason for naming it the way
 he did.

 The question of what it should be named comes down to this:

  * Is kiwi a python module, used by other python software? If so, then it
 would be advantageous to rename it to py-kiwi and to provide subports for
 as many supported versions of python as possible. In this case,
 python.link_binaries_suffix cannot be cleared because it would cause the
 binaries installed by each subport to conflict with each other, which we
 don't want. Also, if this name change is to be made, then all ports
 depending on kiwi (currently only gazpacho and PIDA) need to have their
 dependencies rewritten from kiwi to py*-kiwi, and be tested with the new
 py*-kiwi. For example, do they need changes to be able to find kiwi-i18n
 and kiwi-ui-test with their new suffixes?
  * Is kiwi software that just happens to be written in python, that's used
 by other software that may or may not itself be written in python? If so,
 then the port name should be kept as kiwi. In this case, clearing
 python.link_binaries_suffix is a good idea because it doesn't require
 depending ports to know what version of python kiwi was built for, which
 would be an implementation detail they shouldn't need to care about in
 that case.

-- 
Ticket URL: <https://trac.macports.org/ticket/36022#comment:2>
MacPorts <http://www.macports.org/>
Ports system for Mac OS