public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Rebecca Cran" <rebecca@bsdio.com>
To: devel@edk2.groups.io, spbrogan@outlook.com,
	Ard Biesheuvel <ardb+tianocore@kernel.org>,
	Jiewen Yao <jiewen.yao@intel.com>,
	Jordan Justen <jordan.l.justen@intel.com>,
	Gerd Hoffmann <kraxel@redhat.com>
Cc: 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: Wed, 3 May 2023 14:06:03 -0600	[thread overview]
Message-ID: <8c0bd200-c6d2-3c42-470e-70e0a86d1339@bsdio.com> (raw)
In-Reply-To: <BY3PR19MB490092E74E33E6A58C74C3C4C86C9@BY3PR19MB4900.namprd19.prod.outlook.com>

On 5/3/23 13:50, Sean wrote:

> 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.
>
>
> So my suggestion is to hold off for a couple of weeks (unless 
> something is broken) and lets see if we can use web downloads from 
> github releases.  This should still allow consistency with tools, work 
> cross platform, and give the flexibility needed per platform.
>
That's great news! That would remove a major impediment to using the 
stuart tools for me on FreeBSD, and a hassle getting setup on Linux.

> Regarding the steps in that document.  In that example it doesn't call 
> out all the steps needed as that would just rehash the section 
> before.  Instead it relies on a user having followed the generic steps 
> in the section above (How to Build With Stuart · 
> tianocore/tianocore.github.io Wiki 
> <https://github.com/tianocore/tianocore.github.io/wiki/How-to-Build-With-Stuart#how-to-build-in-edk2-with-stuart>).  
> For example the user would need to have also done:  setup python 
> virtual env, install pypi dependencies, and clone source + submodules.
>
I hadn't realized that .pytool/CISettings.py was for CI and I should 
swap out the platform's UefiBuilder script when running 
stuart_setup/stuart_update.


-- 
Rebecca Cran


  reply	other threads:[~2023-05-03 20:06 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 [this message]
2023-05-04  5:56   ` Gerd Hoffmann
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=8c0bd200-c6d2-3c42-470e-70e0a86d1339@bsdio.com \
    --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