I'm guessing you want to implement this ASAP to get it in use.

I will amend FreshPorts to extract this variable. If I got that work done before this change goes into use, it would capture all future uses. If I don't, it's just a one-off script to refresh the database from the ports tree.

In D59664#1369215, @dvl wrote:

I'm guessing you want to implement this ASAP to get it in use.

I will amend FreshPorts to extract this variable. If I got that work done before this change goes into use, it would capture all future uses. If I don't, it's just a one-off script to refresh the database from the ports tree.

NOTE: I'm just thinking out loud because it helps my planning process.

I don't think freshports needs to extract this, you can keep using build/run, it is only to be used as some kind of syntaxic sugar, and it's mostly to avoid people doing RUN_DEPENDS=BUILD_DEPENDS.

I like it!

FYI, I have code changes in place everywhere but prod. I'm letting them run before updating prod tomorrow. If this could hold off until after that, I would appreciate it as it would avoid work for me. Thanks.

I don't think freshports needs to extract this, you can keep using build/run, it is only to be used as some kind of syntaxic sugar, and it's mostly to avoid people doing RUN_DEPENDS=BUILD_DEPENDS.

oops. I just saw this.

Are you saying that make -V RUN_DEPENDS will still pull back the usual stuff? Same with make -V BUILD_DEPENDS ... hmm.

In D59664#1370294, @dvl wrote:

Are you saying that make -V RUN_DEPENDS will still pull back the usual stuff? Same with make -V BUILD_DEPENDS ... hmm.

It's exactly what the patch does, put BUILD_RUN_DEPENDS into BUILD_DEPENDS and RUN_DEPENDS.