Re: Packaging scrcpy with a precompiled APK dependency.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, 2022-02-16 at 17:57 -0300, Diego Herrera wrote:
Hi. I was checking if the scrcpy software [1] could get packaged, but to continue I need to know how to package an APK package file. For context, this project consists on a Linux client and an Android server app that is uploaded as an APK package by the client to an Android device using adb to share the Android device screen.

The project provides the sources to build that APK file, but it depends on gradle and the Android SDK to build it. Even if we revive the gradle package, I doubt that we can package the Android SDK since it requires it's own set of licenses and I don't think that everything complies to the policies. I also don't know if there is a way to compile the APK without those dependencies.

On the other hand, the project also provides the precompiled APK that can get directly added to the package (that's how other distros package this software), but I doubt that adding a binary package complies with Fedora's policies even if its not used on the same Fedora machine.

Another idea that I thought of was to patch the program or add a script that downloads the APK on the first run and save it on userspace. Technically you are not packaging the binary, but in my opinion it's just a roundabout way to get the same result.

Is any of these approaches viable from a policy perspective? Is there a better way to do this? Or should I desist on packaging this project on Fedora for now?

[1] https://github.com/Genymobile/scrcpy

you got several packages 
from  https://repology.org/project/scrcpy/versions
https://fedora.pkgs.org/34/rpm-sphere-x86_64/scrcpy-1.19-1.x86_64.rpm.html


in copr 
https://copr.fedorainfracloud.org/coprs/fulltext/?fulltext=scrcpy
https://copr.fedorainfracloud.org/coprs/useidel/scrcpy/
https://copr.fedorainfracloud.org/coprs/sixg0000d/scrcpy/
https://copr.fedorainfracloud.org/coprs/zeno/scrcpy/

etc


Best regards.

--
Diego Herrera C.
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure

-- 
Sérgio M. B.
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux