bsdowl: Update to v2.2.1

[michipili (Michael Grünewald)]

This is a simple update to v2.2.1.

References:

• ​https://github.com/michipili/bsdowl/releases/tag/v2.2.1

[michipili (Michael Grünewald)]

Update to v2.1.1

[petrrr]

Cc Me!

[ryandesign (Ryan Carsten Schmidt)]

The configure phase fails:

checking for gawk... gawk
checking for grep that handles long lines and -e... /opt/local/bin/grep
checking for a BSD-compatible install... /usr/bin/install -c
checking whether ln -s works... yes
checking for a thread-safe mkdir -p... /opt/local/bin/gmkdir -p
checking for a sed that does not truncate output... /opt/local/bin/gsed
checking for id that handles -g, -u and -n... id
checking for gm... yes
checking for bmake... no
configure: error: *** BSD Make not found.

The program the bsdmake port provides is called bsdmake not bmake.

[petrrr]

Cc Me!

[ryandesign (Ryan Carsten Schmidt)]

michipili, can you comment on the configure failure I reported above? Do you have a solution?

[michipili (Michael Grünewald)]

This is a missing dependency. The bsdowl port should depend on devel/bmake, for building and running. I can submit a patch in following days.

[michipili (Michael Grünewald)]

This is is bigger problem than I thought.

First, as you ryandesign@… pointed it out, there is two BSD Make programs available in MacPorts:

• bsdmake
• bmake

These programs are very similar but distinct (at least, available versions are not compatible). The bsdowl software is actually compatible with our MacPorts for bmake but not bmake.

Dependencies are not an issue here, rather the build.type. Which value should I pick so that the make command used is bmake -r instead of bsdmake ?

[larryv (Lawrence Velázquez)]

Replying to michipili@…:

Dependencies are not an issue here, rather the build.type. Which value should I pick so that the make command used is bmake -r instead of bsdmake?

There is no value of build.type corresponding to bmake. You will probably need something like this (untested):

depends_build bin:bmake:bmake
build.cmd bmake
build.post_args -r

I’m just guessing that bmake accepts build targets as GNU Make does. You’ll probably have to tweak my example.

[ryandesign (Ryan Carsten Schmidt)]

If I install bmake, that satisfies the configure check. But given the existing "build.type bsdmake" in the Portfile, the port then builds using bsdmake, which seems to work fine. Are we certain bsdowl really requires bmake? If bsdmake will work, we should make that happen, e.g. by bypassing the configure check for bmake as in attachment:bsdowl-2.2.1-ryandesign.diff​.

[ryandesign (Ryan Carsten Schmidt)]

Replying to ryandesign@…:

Are we certain bsdowl really requires bmake?

I ​asked about this in the upstream issue tracker where the developer (who is also this ticket's reporter) explained that more bmake-specific functionality will be used in future versions of bsdowl, so it seems simplest for bsdowl in MacPorts to use bmake after all. We may want to add "build.type bmake" functionality to MacPorts base at some point. For now, since bsdowl will be the first port in MacPorts to use bmake, we can do it manually as Larry suggested. I'll do that and commit the update.

[ryandesign (Ryan Carsten Schmidt)]

r129878

[ryandesign (Ryan Carsten Schmidt)]

And then I realized one of the changes in 2.2.1 is:

​#41 Command mp2png is now implemented using GraphicsMagick

So GraphicsMagick is a runtime dependency as well, and not just a build dependency. So that makes it a library dependency. Changed in r129879.

[michipili (Michael Grünewald)]

Changed in r129879.

Thank you for your help!