...snip... > Packages for the repository are built in COPR. The COPR owner can > propose the repository as a whole for inclusion into the Playground > repository by marking it as such in COPR. Repositories/packages > successfully built and satisfying the Playground repository's > Policies are copied into the Playgroud repository. The one Playground > repository includes many Copr repositories.
I'm a bit confused here. Is there another repo that all playground packages are copied to? Or are they just seperate copr repos? Ok, on further reading there is a seperate repo. This would be mirrored? How is is composed? Just a simple pull all packages from these copr's and createrepo? Will it support multilib, signing, drpms or updateinfo? I see mention that multilib isn't planned at first and that you want to use obs-signd to sign packages. Wouldn't it make sense to look at just using mash (which we use for all other composes). If you did that we could look at signing with sigul and you could get multilib/drpms/etc along for the ride? "To avoid any potential confusion, we want to make it clear that the Playground repository will not host packages that have bad licenses, include proprietary software or include patented software." Might change this to "all packages advertised in the playground must meet the same legal guidelines as packages in Fedora proper". Some software we ship does have patents, just ones that have patent grants attached. Can you expand on: "The repository's repodata is continuously regenerated. All the builds in the COPR repositories that are selected to feed the Playground repository are composed once a day and pushed to the Playground repository and its mirrors." Is the repo composed once a day? Or everytime there is a new build? kevin
signature.asc
Description: PGP signature
-- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
