> So, we pride ourselves on having a 100% free and open infrastructure > software wise. However, we have had some exceptions (the autocloud vbox > test machine, etc). > > For f24, the plan is to make workstation downloads at least prefer to > download a usb media creator, and then that downloads the images, > verifies them and writes them to usb in a sane/best manner. > > Producing the Fedora/linux version of this is no problem, it's just a > package. > > However, windows and osx are a different matter. > > For windows, we could run a windows vm and attach it to koji (it > supports windows builders I think). This would of course mean that we > would need to run a windows builder vm. ;( Or we could have a isolated > hw instance that we only power on for windows builds. Is it possible to use mingw/mingw64 to build the windows binaries, I know it's been used for other projects (although I'm not sure of the exact details). > For osx, I don't think you can virtualize it at all, and koji has no > support, so we would need to have an isolated osx instance available > for building the osx media creator. (possibly only running on demand). > > We could of course just say: sorry, no non free oses in our > infrastructure, but I fear this will result in builds done ad-hock on > someones test machine that aren't reproducible or all the other things > we expect from products we release. ;( Not sure how running windows/OSX in vs out of the infrastructure provides "reproducible builds" in the manner we refer to generally in the context of koji builds (chroots, auditable logs of all the versions of software used to make the builds etc). Either way I'm not particularly opposed to any of the above although TBH it's coming a bit late in the cycle for an official change, did this slip through the change process for infra/rel-eng needing these requirements? Peter _______________________________________________ infrastructure mailing list infrastructure@xxxxxxxxxxxxxxxxxxxxxxx http://lists.fedoraproject.org/admin/lists/infrastructure@xxxxxxxxxxxxxxxxxxxxxxx
