New port: www/screego: Screen sharing server based on WebRTC

[0mp]

Summary

There is nothing special about the software itself; it's just a way to share your screen over the network.

The point of this differential revision is to ask you for a review of handling NPM/Yarn distfiles/dependencies.

[0mp]

Clean up & simplify Yarn handling logic

[0mp]

Clean up DISTFILES regeneration

[tcberner]

Don't take this the wrong way, but this looks like something that tries really hard not to get packaged, and therefore maybe shouldn't.

[0mp]

In D27090#605078, @tcberner wrote:

Don't take this the wrong way, but this looks like something that tries really hard not to get packaged, and therefore maybe shouldn't.

Well, so upstream releases binaries for FreeBSD, so a part could use that. I just wanted to see if we can actually work with yarn dependencies as we work with Go or Rust. It seems like it's possible and not too ugly (apart from the very long list of DISTFILES which almost hits the limit of our do-fetch implementation.

Would you be against me committing the current revision? I don't want to set a bad precedence...

[lwhsu]

In D27090#605279, @0mp wrote:

In D27090#605078, @tcberner wrote:

Don't take this the wrong way, but this looks like something that tries really hard not to get packaged, and therefore maybe shouldn't.

Well, so upstream releases binaries for FreeBSD, so a part could use that. I just wanted to see if we can actually work with yarn dependencies as we work with Go or Rust. It seems like it's possible and not too ugly (apart from the very long list of DISTFILES which almost hits the limit of our do-fetch implementation.

Would you be against me committing the current revision? I don't want to set a bad precedence...

IMHO, this seems still aligning with the practices in the ports, and I don't think it should be blocked to go into the tree. Enable users to use good 3rd party is important.

For the long run, I feel we need something better in ports infra or tooling to maintaining these go/rust/yarn ports.

[0mp]

In D27090#605281, @lwhsu wrote:

For the long run, I feel we need something better in ports infra or tooling to maintaining these go/rust/yarn ports.

Just a note you might find interesting: portedit from the ports-mgmt/portfmt is already helping a lot.