[MacPorts] #61861: gimp-resynthesizer: uses "python2", underquoted AC_CONFIG_HEADERS, lib dependency, license

[MacPorts]

#61861: gimp-resynthesizer: uses "python2", underquoted AC_CONFIG_HEADERS, lib
dependency, license
---------------------------------+----------------------
  Reporter:  ryandesign          |      Owner:  pietvo
      Type:  defect              |     Status:  assigned
  Priority:  Normal              |  Milestone:
 Component:  ports               |    Version:
Resolution:                      |   Keywords:
      Port:  gimp-resynthesizer  |
---------------------------------+----------------------

Comment (by ryandesign):

 Replying to [comment:1 pietvo]:
 > Re: the `python2`:  almost all standard python plugins in `gimp2` have
 `#!/usr/bin/env python2`

 Then they are all broken on macOS 10.14 and earlier and need to be fixed.

 > `gimp2` has the default variant `+python27`, so usually the dependency
 on `python2.7` is already satisfied. But if `gimp2` is installed with
 `-python27` then all hope is lost, because the plugin won't work. Is there
 a way to set a dependency on `gimp2` with the `python27` variant enforced?

 This can be accomplished using the `require_active_variants` procedure of
 the active_variants 1.1 portgroup.
 {{{
 PortGroup active_variants 1.1
 require_active_variants path:lib/pkgconfig/gimp-2.0.pc:gimp2 python27
 }}}

 > Re: the `lib:libgimp-2.0:gimp2`, this was done to catch also
 `gimp2-devel`. Is there a way to specify either `gimp2` or `gimp2-devel`?

 Other ports use `path:lib/pkgconfig/gimp-2.0.pc:gimp2`

 > And, by the way, I also noticed a few `python3` scripts in the `gimp`
 distribution, whereas the `gimp2` port has no dependency on any `python3`.
 That is of course outside this port, but maybe it should be looked int.

 No port provides `python`, `python2`, or `python3`. All OS versions
 provide /usr/bin/python. Some OS versions provide /usr/bin/python2 or
 /usr/bin/python3 but not all so you shouldn't rely on them. Symlinks
 called python, python2 or python3 can be created by using `port select
 python` but that is for the user's convenience only; ports should not rely
 on the user having run (or not run) `port select`. If you can use any
 python and don't care what version and don't need any extra modules,
 `#!/usr/bin/env python` is fine or `#!/usr/bin/python` if you want to
 ensure that a MacPorts python will not be used. If you care what version
 or you need extra modules, specify a dependency on the corresponding
 python and module ports and use `#!/opt/local/bin/pythonX.Y` where X.Y is
 whatever version you're using.

-- 
Ticket URL: <https://trac.macports.org/ticket/61861#comment:2>
MacPorts <https://www.macports.org/>
Ports system for macOS