Hi, > I agree the iasl dependency for CI has not been managed consistently. When > all of the CI was setup we decided that iasl should be controlled by the > platform and thus EmulatorPkg, ArmVirt, and OVMF have their own extdep. > This gives those platforms control to rev their version as necessary for > their platform. We have found it very common in platform development for > platforms to have different required versions of iasl.exe.
Are there cases where /old/ iasl versions are required? > As for the feed. Yes they are inconsistent. We were moving away from a > global nuget.org feed as it just didn't seem necessary to push to > nuget.org. But now we are evaluating ways to move entirely away from > nuget. Nuget.exe worked pretty well for Windows development and our initial > use cases but has definitely created a headache on Linux, MacOS and other. > There really isn't a generic package management solution that is supported > cross platform that has free/high quality/secure hosting. If anyone has > ideas please share. On linux / macos / *bsd there is usually no need to create your own package management. Standard stuff like iasl / nasm is available as linux distro package / bsd ports collection package. Usually you can't pick specific versions. Usually this isn't a big issue though, unless you are using an older distro (such as ubuntu 18.04 we used for CI before switching to containers) and need a recent version. take care, Gerd -=-=-=-=-=-=-=-=-=-=-=- Groups.io Links: You receive all messages sent to this group. View/Reply Online (#103954): https://edk2.groups.io/g/devel/message/103954 Mute This Topic: https://groups.io/mt/98669896/21656 Group Owner: devel+ow...@edk2.groups.io Unsubscribe: https://edk2.groups.io/g/devel/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
