[MacPorts] #64083: New port -- m2vrequantiser

[MacPorts]

#64083: New port -- m2vrequantiser
-----------------------------+------------------------
  Reporter:  RobK88          |      Owner:  ryandesign
      Type:  submission      |     Status:  accepted
  Priority:  Normal          |  Milestone:
 Component:  ports           |    Version:  2.7.1
Resolution:                  |   Keywords:
      Port:  m2vrequantiser  |
-----------------------------+------------------------
Changes (by ryandesign):

 * status:  new => accepted
 * owner:  (none) => ryandesign


Comment:

 "Universal" in MacPorts means multiple architectures. Which specific
 architectures depends on the `universal_archs` setting in macports.conf.
 The default value of that setting varies by OS version.

 `use_xz yes` doesn't do anything strange. It sets the `extract.suffix` to
 `.tar.xz`, changes `extract.cmd` to `xz`, and adds the xz extract
 dependency.

 MacPorts base does as of recently contain code that automatically creates
 a symlink to your source directory, to assist you if you have neglected to
 set `worksrcdir` correctly. I do not recall how this code is intended to
 behave if you have multiple distfiles. (If you have just one distfile that
 extracts to just one directory, then it's obvious what the symlink should
 point to, otherwise it's not so obvious.)

 The Portfile doesn't work for me. It fails to download the debian file.

 Is the debian file still needed at all? Your latest zip file has a files
 directory containing three patchfiles which is all that the Portfile
 references. Isn't that all we need? It seems to build fine if I remove the
 debian distfile stuff.

 If we were using the second distfile, then you should have listed
 `extract.only`, specifying which distfile MacPorts should extract, but
 since I don't think we need the second distfile it's moot.

 Yes, the Makefile should probably set CC only if the user hasn't already
 set it as an environment variable. You should suggest that to the
 developer. In MacPorts when using the makefile 1.0 portgroup it doesn't
 matter since the makefile 1.0 portgroup specifies CC as an argument (which
 overrides variables set by the Makefile) rather than as an environment
 variable (which would be overridden by the Makefile).

 Yes, you can verify whether a file is universal by using `file`, or `lipo
 -info`.

 ...Oh I see, in the destroot phase you install a manpage which comes from
 the debian distfile. Is that the only thing from the debian distfile that
 we need? If so, let's just put it in the files directory too. (By the way,
 manpages don't need to be installed with the execute bit.)

 I'll attach my new proposed Portfile.

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