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"
signature.asc
Description: This is a digitally signed message part.
