• Re: Intend to package Cuttlefish (Android virtual device)

    From Andrew M.A. Cater@21:1/5 to All on Wed Aug 28 22:40:01 2024
    On Thu, Aug 29, 2024 at 04:20:20AM +0800, Ying-Chun Liu (PaulLiu) wrote:
    Hi all,

    I intend to package Cuttlefish. But I'd like some clarification.

    Cuttlefish, an open-source project (source: https://source.android.com/docs/devices/cuttlefish/get-started), requires downloading or building additional open-source components like AOSP images and crosvm for full functionality.

    For the meanwhile, we need to put this package into "contrib". Am I right?

    The concept of "contrib" typically refers to packages that depend on
    non-free components, even if the package itself is open-source. However, in this case, the required tools might not be officially packaged for Debian yet. While they are all open-source, their absence from Debian repositories could justify placing Cuttlefish in the "contrib" section. Am I correct?


    Hi,

    If all components are free software with acceptable licences and freedom to distribute the results - this should be able to go into Debian main
    though not yet into Debian stable. If it gets into unstable and testing, it could be released with Debian 13 Trixie when it releases.

    Hope this helps,

    Andy
    (amacater@debian.org)

    Yours,
    Paul

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Judit Foglszinger@21:1/5 to All on Thu Aug 29 06:41:58 2024
    Hi,

    I intend to package Cuttlefish. But I'd like some clarification.

    Cuttlefish, an open-source project (source: https://source.android.com/docs/devices/cuttlefish/get-started), requires downloading or building additional open-source components like AOSP images and crosvm for full functionality.

    For the meanwhile, we need to put this package into "contrib". Am I right?

    The concept of "contrib" typically refers to packages that depend on non-free components, even if the package itself is open-source. However, in this case, the required tools might not be officially packaged for Debian yet. While they are all open-source, their absence from Debian repositories could justify placing Cuttlefish in the "contrib" section. Am I correct?

    If all components are free software with acceptable licences and freedom to distribute the results - this should be able to go into Debian main
    though not yet into Debian stable. If it gets into unstable and testing, it could be released with Debian 13 Trixie when it releases.

    Depends on how strong the dependency is [1], what depends of how relevant the missing functionality is.
    Rather "nice to have but unneeded" or more like "people would expect this to work, when using this software"
    or even "this software is useless without this functionality"?

    [1]
    https://www.debian.org/doc/debian-policy/ch-archive.html#the-main-archive-area

    "packages in main
    must not require or recommend a package outside of main for compilation or execution
    (thus, the package must not declare a Pre-Depends, Depends, Recommends, Build-Depends,
    Build-Depends-Indep, or Build-Depends-Arch relationship on a non-main package"


    -----BEGIN PGP SIGNATURE-----

    iQIzBAABCgAdFiEEeh+1J5uI1UvU9CMA9TaqcBEdVxYFAmbPmaYACgkQ9TaqcBEd Vxbiwg//W73Mu3h6wvKes/s+NiTVkLwR2mpZ4V+lj9wrqi23EpV2LlhdXToNNiNI /vAsVTY5ZEqIrIZlft8a7+JnYpH5iLs0m7bUkvTgP4oVYBT+JuWMwmyrBmwEDxMn yTBptvbel9f/Q+JlwT/QSYeTz1QY8PKy9SwPobFgEcK/KVRQP29BSIN0RgcBv1CW G/Jc4zDiyZZJlP7GhmL3L++5AiwOFLDXFjbyvAWSbQ1F/a9qFKIR3nfkD85ew7rB JSVjOQXwmn5HY4SgzA+NH8ZpfJLuAEcne8Whg+VOIcjjHxeHHaXK0Hp4WuWfWDJq WtSrcSdFctuVX7wndZGoFfXOoTCXbLklaeWNkf3KU+PYgBD0ovNxTm9tQx1af056 /iV1enkZbrVkAXXpvEIsmFePqeOyiVZTRcWA4xiTDrn/YGWSxHanKaSApg+34KBd RM5klTlmpECEiBaRvKM/ZMKVWKvFlPh8NojJt4VzFspCufk0ZPff4cX3WM0k+WCp cxllUMaojiwbdYlNKAGcs1b71vTmwQmuhQzkwa0ur64EC5XRw+cuYqQ+NsIzGbmY lBCfxj9k6LdiW0h1Jzex0F0NOUCk/9MnAnUunDlzHoTXhMVzNg6O7OA6d2sSI2u9 ntpISggBHI+l04ds+PbtDdVmPN8CMDs8RI3QSxnnYcQpCRs8wjw=
    =ukrf
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)