You can either;
- repack with submodules and host
- set additional DISTFILES+MASTER_SITES for the submodules (example in ntopng)
- ask upstream if they'll generate and upload a tarball as a release asset
like they do with binaries - like irssi, darktable, jq, liferea and many others
--
Sent from a phone, apologies for poor formatting.
On 9 December 2019 06:43:26 Brad DeMorrow <brad@demorrow.net> wrote:
> I managed to get moonlight-qt (to stream games) to work today.
> I'm trying to bundle up my work, but I need some help/feedback on a few
> things.
>
>
> First, here is libva and the intel-vaapi-driver.
> I've ran portcheck and done several clean/build cycles and it works on my
> box,
> but I'm still pretty new to porting - so it's probably not perfect.
>
>
> Both required very minimal patching to get them to compile. I will try
> to upstream these patches in a better way, but they are in the tree for the
> moment.
>
>
> Beyond these two, I have attached a small update to the graphics/ffmpeg
> Makefile
> that simply enables VAAPI and allows hardware-accelerated H264 decoding from
> moonlight-qt. I was able to stream games on my local network at 60FPS@1080p
> without a problem.
>
>
> Now for the big question/problem:
> moonlight-qt requires a `git submodule update --init --recursive` before
> the build, but
> I'm pretty sure that's not how we do things here. How is this normally
> handled?
> Do I need to repack everything and host it on my own github account?
>
>
> Feedback appreciated.
No comments:
Post a Comment