From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by mx.groups.io with SMTP id smtpd.web11.43035.1683179775980210963 for ; Wed, 03 May 2023 22:56:16 -0700 Authentication-Results: mx.groups.io; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=NyeUEvcP; spf=pass (domain: redhat.com, ip: 170.10.133.124, mailfrom: kraxel@redhat.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1683179774; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=UAMq7i9IfNjgFsS4GtRd3s+4ReCH0vFoy2B1KHezq8A=; b=NyeUEvcPM97dbQfrOMS83D/pYgQpFTES1US6WbxpzKZpXJ1BDiS/0xaXGvXJAUYOuTXb7e R8CLzm+qMfsgCWa5Sd/ywbauE5xmBlhua7AnzUA5LQbubM3f5AnYhOco80l0bycXpNSSZr D/EficSQ9KfLaqRjNl87IJY/7T6LB3s= Received: from mimecast-mx02.redhat.com (mimecast-mx02.redhat.com [66.187.233.88]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-300-VyROhiCbNB-LwGbRNLrYRA-1; Thu, 04 May 2023 01:56:11 -0400 X-MC-Unique: VyROhiCbNB-LwGbRNLrYRA-1 Received: from smtp.corp.redhat.com (int-mx05.intmail.prod.int.rdu2.redhat.com [10.11.54.5]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 99E75185A78B; Thu, 4 May 2023 05:56:10 +0000 (UTC) Received: from sirius.home.kraxel.org (unknown [10.39.192.48]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 3B20C63F5F; Thu, 4 May 2023 05:56:10 +0000 (UTC) Received: by sirius.home.kraxel.org (Postfix, from userid 1000) id D72CC180061F; Thu, 4 May 2023 07:56:08 +0200 (CEST) Date: Thu, 4 May 2023 07:56:08 +0200 From: "Gerd Hoffmann" To: Sean Brogan Cc: devel@edk2.groups.io, rebecca@bsdio.com, Ard Biesheuvel , Jiewen Yao , Jordan Justen , Sean Brogan , Michael Kubacki , Michael D Kinney , Liming Gao Subject: Re: [edk2-devel] OvmfPkg PlatformCI: Should iasl dependency be updated from 20190215.0.0 ? Message-ID: References: <5970efe0-b520-f92d-db2f-6ed809ce4e55@bsdio.com> MIME-Version: 1.0 In-Reply-To: X-Scanned-By: MIMEDefang 3.1 on 10.11.54.5 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit 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