libjpeg-turbo @1.3.1_0: update to 1.4.0

[RJVB (René Bertin)]

As offered on the ML, here's an update to port:libjpeg-turbo .

[RJVB (René Bertin)]

One could use the following conflict statement to let the port co-exist with jpeg 9+ installed in its own prefix (cf. #47808)

conflicts           mozjpeg
if {[file exists ${prefix}/lib/libjpeg.dylib]} {
    conflicts-append jpeg
}

BTW, this update does not yet include the versioning scheme update that I proposed (which would make this version 8:1.4.0 or 8.1.4.0).

[mkae (Marko Käning)]

Cc Me!

[ryandesign (Ryan Carsten Schmidt)]

Changing the dependency from port:nasm to bin:nasm:nasm will fail if /usr/bin/nasm exists and ${prefix}/bin/nasm does not exist because of the configure argument NASM=${prefix}/bin/nasm. Why make this change?

[ryandesign (Ryan Carsten Schmidt)]

You don't need to check if {[variant_exists universal] && [variant_isset universal]} because the merger_host and merger_configure_args variables that are being set are only used by the muniversal portgroup when the universal variant is set.

[RJVB (René Bertin)]

Replying to ryandesign@…:

You don't need to check if {[variant_exists universal] && [variant_isset universal]} because the merger_host and merger_configure_args variables that are being set are only used by the muniversal portgroup when the universal variant is set.

OK, makes sense. I just copied what I saw elsewhere.

[RJVB (René Bertin)]

Replying to ryandesign@…:

Changing the dependency from port:nasm to bin:nasm:nasm will fail if /usr/bin/nasm exists and ${prefix}/bin/nasm does not exist because of the configure argument NASM=${prefix}/bin/nasm. Why make this change?

Ah, right. In fact I tried this syntax to see if it allowed me to build +universal without installing nasm+universal, before port:nasm got updated.

[larryv (Lawrence Velázquez)]

r136586:136595