public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Gerd Hoffmann" <kraxel@redhat.com>
To: Sean Brogan <spbrogan@outlook.com>
Cc: devel@edk2.groups.io, rebecca@bsdio.com,
	 Ard Biesheuvel <ardb+tianocore@kernel.org>,
	Jiewen Yao <jiewen.yao@intel.com>,
	 Jordan Justen <jordan.l.justen@intel.com>,
	Sean Brogan <sean.brogan@microsoft.com>,
	 Michael Kubacki <mikuback@linux.microsoft.com>,
	Michael D Kinney <michael.d.kinney@intel.com>,
	 Liming Gao <gaoliming@byosoft.com.cn>
Subject: Re: [edk2-devel] OvmfPkg PlatformCI: Should iasl dependency be updated from 20190215.0.0 ?
Date: Thu, 4 May 2023 07:56:08 +0200	[thread overview]
Message-ID: <wjnvqofpwfz7mehjjr5iglwpdu5k4nmwyhssvkycjmeltafzne@mgz4dssphdqs> (raw)
In-Reply-To: <BY3PR19MB490092E74E33E6A58C74C3C4C86C9@BY3PR19MB4900.namprd19.prod.outlook.com>

  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


  parent reply	other threads:[~2023-05-04  5:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-03 19:34 OvmfPkg PlatformCI: Should iasl dependency be updated from 20190215.0.0 ? Rebecca Cran
2023-05-03 19:50 ` [edk2-devel] " Sean
2023-05-03 20:06   ` Rebecca Cran
2023-05-04  5:56   ` Gerd Hoffmann [this message]
2023-05-05  3:13     ` Sean
2023-05-04 17:21   ` Michael D Kinney
2023-05-05  2:17     ` Michael Kubacki

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-list from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=wjnvqofpwfz7mehjjr5iglwpdu5k4nmwyhssvkycjmeltafzne@mgz4dssphdqs \
    --to=devel@edk2.groups.io \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox