From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-io1-f49.google.com (mail-io1-f49.google.com [209.85.166.49]) by mx.groups.io with SMTP id smtpd.web12.9512.1599003330444205225 for ; Tue, 01 Sep 2020 16:35:30 -0700 Authentication-Results: mx.groups.io; dkim=pass header.i=@gmail.com header.s=20161025 header.b=GLGSR5xX; spf=pass (domain: gmail.com, ip: 209.85.166.49, mailfrom: matthewfcarlson@gmail.com) Received: by mail-io1-f49.google.com with SMTP id r9so3868846ioa.2; Tue, 01 Sep 2020 16:35:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=PrbBwfnQhG82iyvBl6+xzNEmHYutMpDyO1b9R2BNO6g=; b=GLGSR5xXXKkrVbh3rA2PKwKFuVj0b+pFhS41WJwFAsKo2JM9uTkzSABjSSilMDxvLV /DPADzPGRn4ikB5prp5fVAlZOP3SNE502YUhzNC0yPGfgsOjM16RPVYNVCviyg0mttZ2 alYsOWGnGfsRvpCVhHn+lpBzDlrv7RO9GJfspIphbnx8hJof4ztG0PZNwdhiAe1BYyW/ GK59R3v3BqUXf2PW6gH8NP5jsDvdXB/c9muGPCjv/b/trifSgJEoJfjFkQNBQSlUs8G0 qs5CngfuqGpnHeSmehO0NC2UXaWwn+2b6iVXp50+rfG7yzzxNMlvB+NSR0e3CXp3QoQ8 SoQw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=PrbBwfnQhG82iyvBl6+xzNEmHYutMpDyO1b9R2BNO6g=; b=W99Kf3muLHFrdizDYbg4QD0lCulSeyiJ5IMuNpm4qD4DqqprX7Igwo4Axxv1oDWH5M Y8Evvcw9eT7hjCKVQAtdA7V0KkfI0YTKLca2mExBj1YnsnoDvu1sNp9Y5YEC/bYQLSBo ajerEc8iO/hSxii8jx5Fnn0s/GBvL+GhwsratijXPECMsxCVNBzyZSUOkQmc++rlezA/ 7dqViRom7R/1f1CTb54kolHhV3Pc6wj6POPWhXHfd1HZRJQO9vXE1qu8hnRc8r+8kIpd O5wJJIhaH/sA8njOMqcZYJHX+X1jWAcZ6d/gm4PsGNHbx9Rlv1XSk4kl/Sy1msUZcx9g EviA== X-Gm-Message-State: AOAM532YYrN/2TykgiFYHT35xD/2k4mer/pGinqi/xGkLgINQsOWGxKW Kz1GbnTcDfk+8OvJrjG4qN1ulj541duCO/S0aUADCeBndE+7kI9U X-Google-Smtp-Source: ABdhPJz5BZUSaG5tmkhUox+xjP90bV7XjJQNT6hylNi7E27mL496spGzSED9irXYwnEZagSiWAMRuTU1r8x9u1BdXGA= X-Received: by 2002:a6b:7846:: with SMTP id h6mr1245410iop.145.1599003329483; Tue, 01 Sep 2020 16:35:29 -0700 (PDT) MIME-Version: 1.0 From: "Matthew Carlson" Date: Tue, 1 Sep 2020 16:35:17 -0700 Message-ID: Subject: Basetools as a pip module To: rfc@edk2.groups.io, devel@edk2.groups.io Content-Type: multipart/alternative; boundary="00000000000072da1705ae48f976" --00000000000072da1705ae48f976 Content-Type: text/plain; charset="UTF-8" Hello all, A recent topic on the RFC mailing list went out and the work on moving Basetools/Sources/Python to a separate repo has started. See the RFC conversation here: https://edk2.groups.io/g/rfc/topic/74009714#270 The repo in question is here: https://github.com/tianocore/edk2-basetools The current plan is shortly after the stable tag is created, a series of patches will come into edk2 that redirects the build system into the new python module as well as adds additional documentation. You can see a sample of this work here: https://github.com/matthewfcarlson/edk2 as this has a branch that has the work required to use the basetools pip module. The patches won't delete the Basetools/Sources/Python folder but will allow users to select between them. After a certain grace period, the python folder will be deleted and the pip module will be the de facto way of using basetools. Three questions need to be answered: 1. After the patches that enable the pip module land, how long should the grace period be? 2. During the grace period, should basetools commits land in both places or just in the edk2-basetools directory? 3. How should the user be able to select which basetools to use (the one in EDK2 or the pip module)? Currently the approach being considered is a simple environmental variable? One of the key considerations is transparency since it won't be apparent what is being used for a particular build without some sort of mechanism to notify the developer. With two seperate versions of Basetools, it becomes very easy for the version of basetools you're using to not be the one you expect. Thank you. -Matthew Carlson --00000000000072da1705ae48f976 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hello a= ll,

A recent topic on the RFC mailing list went out and = the work on moving Basetools/Sources/Python to a separate=C2=A0repo has sta= rted. See the RFC conversation here:=C2=A0https://edk2.groups.io/g/rfc/topic/74009714#270<= /a>


The current plan is shortly afte= r the stable tag is created, a series of patches will come into edk2 that r= edirects the build system into the new python module as well as adds additi= onal documentation. You can see a sample of this work here:=C2=A0https://github.com/matthewfcarlso= n/edk2=C2=A0as this has a branch that has the work required to use the = basetools pip module. The patches won't delete the Basetools/Sources/Py= thon folder but will allow users to select between them. After a certain gr= ace period, the python folder will be deleted and the pip module will be th= e de facto way of using basetools.

Three questions= need to be answered:

1. After the patches that en= able the pip module land, how long should the grace period be?
2.= During the grace period, should basetools commits land in both places or j= ust in the edk2-basetools directory?
3. How should the user be ab= le to select which basetools to use (the one in EDK2 or the pip module)? Cu= rrently the approach being considered is a simple environmental variable? O= ne of the key considerations is transparency since it won't be apparent= what is being used for a particular build without some sort of mechanism t= o notify the developer. With two seperate versions of Basetools, it becomes= very easy for the version of basetools you're using to not be the one = you expect.

Thank you.
-Matthew Carlson
--00000000000072da1705ae48f976--