On Tue, Jan 08, 2019 at 12:28:51PM -0500, Owen Taylor wrote: > * Reduce some confusion. A Flatpak is a module, but it’s *also* a > container, and the dist-git repository will include files for both. I'm +1 to this for this reason. I think it's less confusing than the downside loose-module confusion. :) In related news, I'm killing the rawtherapee "loose-rpm" module and just making a flatpak one. Question: would this open up the possiblity of offering different _flatpak_ streams? I'd like to have a stream where the rc releases are built so people who want to try those can. > * We should probably move flatpak-common to the flatpaks/ namespace > for ease of discovery, but it isn’t in any way a flatpak, it’s just a > module that Flatpaks can depend on. I'd suggest just making a flatpak-common repo in flatpaks/ with a README linking to the module namespace. -- Matthew Miller <mattdm@xxxxxxxxxxxxxxxxx> Fedora Project Leader _______________________________________________ infrastructure mailing list -- infrastructure@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to infrastructure-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@xxxxxxxxxxxxxxxxxxxxxxx
