mathaeus

I already created a PR for updating the `SDWebImage` dependency to `4.0.0`, see https://github.com/mwaterfall/MWPhotoBrowser/pull/591.

@sureshdagooglecom did you have some time to have a look at my suggested changes? Is this something that the Mediapipe team can take care of or do you prefer me...

@kuaashish pinging you in the hope to get some feedback :)

Bumping this 😬 @sureshdagooglecom is this something that the Mediapipe team is planning to look into?

@joshdholtz sorry to tag you, are you aware of this? :)

While the README is not perfect about it, it is supported. See https://github.com/mono0926/LicensePlist#--package-path

@marci0907 What you need is the `--package-path` I use such a script to wrap the call to the `license-plist` binary with all the parameters: ``` #!/bin/sh GIT_ROOT_DIR=$(git rev-parse --show-toplevel) ${GIT_ROOT_DIR}/scripts/license_acknowledgements/license-plist...

The original issue is talking about _using_ `licence-plist` to generate the licenses output file _based on your SPM dependencies_, not how to _integrate_ `licence-plist` itself via SPM. But to answer...

@sugitatestblue as I mentioned [above](https://github.com/mono0926/LicensePlist/issues/151#issuecomment-1098178378), this issue is about running `LicensePlist` on your SPM dependencies, NOT to install it via SPM.

@sugitatestblue kind of, yes. In my opinion SPM doesn't offer the same "flexibility" as cocoapods when it comes to installing dependencies that work on the project alongside the dependencies that...