On Thu, Aug 20, 2020 at 12:09:08AM +0200, gregor herrmann wrote: > > > > > Are these acceptable caveats for a source package in contrib, > > > > No, the package still needs to be built without network, using only its > > > > contents and packages from Debian. > > > > You also need to produce a package that can be installed with apt and usable > > > > after that, as I'm not sure how is your current package supposed to get the > > > > deps needed to run it. > > > > > > I'm a little confused, then: > > > https://www.debian.org/doc/debian-policy/ch-archive.html#the-contrib-archive-area > > > told me that packages included in contrib included "free packages which > > > require contrib, non-free packages or *packages which are not in our > > > archive at all* for compilation or execution" (emphasis mine); and > > > wouldn't the dependency on dotnet-sdk-3.1 count under the last of those? > > AFAIK the working is too careful, and nobody actually uploads contrib > > packages that download stuff needed for building, even though that's not > > forbidden by the Policy and the buildds not necessarily disable network > > access. I may be wrong, of course. > > libdbd-oracle-perl is such an example; it's in contrib because it's > free software itself but needs oracle software which is not even in > Debian. Typically someone builds it by installing the needed stuff in > a local cowbuilder etc. chroot and then uploads the binary packages. So its next upload will never migrate? -- WBR, wRAR
Attachment:
signature.asc
Description: PGP signature