Open main-- opened 7 years ago
However, another possibility would be simply to add the re-packaged iso to the git-repository.
Disadvantages:
Advantages:
The isos are (as far as I can see) licensed under GPLv2, which shouldn't be a problem for what we do, since we're definitly open-sourcing the derivate of it.
I really don't like that for one big reason: These drivers aren't static. There are bugfixes every now and again and unless we make sure to regularly update them (needlessly committing loads of ISO blobs to the repo in the process), users are kinda stuck with old versions.
IMO, grabbing this during the packaging process right from the source is by far the best solution as it solves all of that with the only downside of requiring more dev dependencies (something I consider to be negligible as you can build a package once and install it many times - plus these packages are neither exotic nor large - I have to temporarily install a JVM whenever I update my audio player ffs!).
Apparently there might be compatibility issues with floppy.
The floppy was neat because it contained exactly what we need (the only alternative they offer is the full ISO with i386 and all drivers and it's literally 50x the size) but that doesn't matter when it doesn't actually work.
I'd suggest repackaging the vfd to an iso (like
mcopy -i virtio-win_amd64.vfd -s ::/amd64 .
) but that's an mtools dependency so not sure.