On Wed, Feb 18, 2026 at 5:08 PM Richard W.M. Jones <[email protected]> wrote: > > On Wed, Feb 18, 2026 at 10:52:26AM -0500, Stephen Gallagher wrote: > > On Wed, Feb 18, 2026 at 7:43 AM Richard W.M. Jones <[email protected]> > > wrote: > > > > > > This is a huge Microsoft monorepo: > > > > > > https://github.com/microsoft/Windows-driver-samples > > > > > > It's distributed under MS-PL, see earlier discussion: > > > > > > https://lists.fedoraproject.org/archives/list/[email protected]/thread/ZSVCFJFVMLTODFKGV352TYHH5ZQODJXD/ > > > > > > For virt-v2v we want a single tool called devcon. The tool will get > > > copied into Windows VMs during conversion to allow some drivers to be > > > uninstalled. Devcon is just a few files: > > > > > > https://github.com/microsoft/Windows-driver-samples/tree/main/setup/devcon > > > > > > vs the entire repo (3590 files in countless directories). > > > > > > I built an RPM already for testing. The source tarball is 15 MB > > > compressed if I include the entire repo, or 38K if I include only the > > > source files needed to compile devcon. > > > > > > Any thoughts on this? Also about naming? > > > > > > I suspect it's unlikely we'd ever need anything else from the monorepo > > > in Fedora. > > > > > > > I'd suggest handling it like a repo with non-redistributable code: > > write a script that pulls the upstream 15MiB tarball down, strips out > > everything except what you plan to ship and then include the script > > and the "sanitized" tarball in the package. > > I do sort of something like this, but using git-archive, what do you think? > > https://bugzilla.redhat.com/show_bug.cgi?id=2440652 > http://oirase.annexia.org/reviews/devcon/mingw-devcon.spec >
To the best of my knowledge, that's exactly what you should be doing. As far as naming, you *might* want to name it something like mingw-windrivers-devcon so that if you ever needed to grab another portion of it, it's clear where it came from, but that's purely an aesthetic choice, since there's no upstream guidance on how to name it. -- _______________________________________________ devel mailing list -- [email protected] To unsubscribe send an email to [email protected] Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/[email protected] Do not reply to spam, report it: https://forge.fedoraproject.org/infra/tickets/issues/new
