Opened 5 years ago

Closed 3 years ago

#36022 closed update (fixed)

kiwi: rename to py-kiwi

Reported by: cawka (Alex Afanasyev) Owned by: petrrr
Priority: Normal Milestone:
Component: ports Version:
Keywords: haspatch Cc: ryandesign (Ryan Schmidt), petrrr
Port: kiwi py-kiwi

Description (last modified by petrrr)

The current version of kiwi port requires python26 and does not use python group.

The updated version Portfile changes the name of the port to py*-kiwi, as well as uses python group to allow use of different versions of python.

Attachments (1)

Portfile (1.8 KB) - added by cawka (Alex Afanasyev) 5 years ago.

Download all attachments as: .zip

Change History (9)

Changed 5 years ago by cawka (Alex Afanasyev)

comment:1 Changed 5 years ago by cawka (Alex Afanasyev)

Forgot to mention. The new Portfile also upgrades version of kiwi (from 1.9.26 to 1.9.29)

comment:2 Changed 5 years ago by ryandesign (Ryan Schmidt)

  • Cc ryandesign@… added
  • Keywords haspatch added
  • Summary changed from unification of kiwi port: py*-kiwi to kiwi: change to py-kiwi, add python 2.7 support, update to 1.9.29
  • Type changed from enhancement to update

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.

comment:3 Changed 5 years ago by cawka (Alex Afanasyev)

kiwi is a python module that is imported in other python scripts. Similarly to the described in 2010 ticket (#24093), I'm using kiwi as part of ns3 visualizer module (python-based).

I can try to run basic tests with gazpacho and PIDA with updated dependencies.

comment:4 Changed 3 years ago by petrrr

  • Description modified (diff)
  • Port py-kiwi added
  • Summary changed from kiwi: change to py-kiwi, add python 2.7 support, update to 1.9.29 to kiwi: rename to py-kiwi
  • Version 2.1.2 deleted

kiwi is now @1.9.29_1 and installs against python 2.7. So this ticket was partly implemented, only renaming is missing.

comment:5 Changed 3 years ago by petrrr

  • Cc petr@… added

Cc Me!

comment:6 Changed 3 years ago by petrrr

  • Owner changed from macports-tickets@… to petr@…
  • Status changed from new to assigned

comment:7 Changed 3 years ago by petrrr

Port renamed in r134071.

comment:8 Changed 3 years ago by petrrr

  • Resolution set to fixed
  • Status changed from assigned to closed
Note: See TracTickets for help on using tickets.