public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "tlaronde@polynum.com" <tlaronde@polynum.com>
To: devel@edk2.groups.io
Cc: Andrew Fish <afish@apple.com>,
	Leif Lindholm <quic_llindhol@quicinc.com>,
	Michael D Kinney <michael.d.kinney@intel.com>
Subject: edk2setup.sh shortcomings
Date: Thu, 2 Feb 2023 12:29:32 +0100	[thread overview]
Message-ID: <Y9uenIaO7PuG04pi@polynum.com> (raw)

edk2setup.sh has shortcomings. To list some:

	- The functions return a status but it is not tested; hence the
	  script goes to the end with a final "return $?" that simply
	  returns the status of the last command that is "unset" which
	  always successfully unsets, even a not set variable. Hence a
	  script can not catch a failure by testing the end status that is
	  always 0;
	- If WORKSPACE is set, --reconfig does nothing;
	- If EDK_TOOLS_PATH and PACKAGES_PATH are set, even to incorrect
	  values, the script succeeds even if BaseTools/ is not found
	  anywhere;
	- The comments are obsolete (1): bash(1) is required because the syntax
	  is not POSIX.2 sh(1) compliant and because some Makefile recipes
	  have "bash'isms" (indeed, a GMAKE variable should be exported
	  with a definition of "/path/to/gnu/make SHELL=/path/to/bash" and
	  a canonical call should be "$GMAKE ...");
	- The comments are obsolete (2): CYGWIN is not treated in anyway
	  specifically and, on the contrary, the regexp translation of ':'
	  in spaces for PACKAGES_PATH would be sure to create a mess with
	  a MS Windows like path;
 	- The settings have obviously evolved and the help message does not
	  list all the variables that can be set and that do modify the
	  way the setting is done;
	- Some commands (notably whereis(1)) are not standard utilities, not
	  to be found on all Unix like systems and, even if found, have
	  greatly diverging behaviors.

What is the preferred procedure? Should I file BZ to list all the
problems so that someone authorized may address them? Or can I propose
a patch to address these (keeping it backward compatible with a present
correct use) with a reasonable hope that, as an exception that will not
become a rule, it will not be ignored?

Best,
-- 
        Thierry Laronde <tlaronde +AT+ polynum +dot+ com>
                     http://www.kergis.com/
                    http://kertex.kergis.com/
Key fingerprint = 0FF7 E906 FBAF FE95 FD89  250D 52B1 AE95 6006 F40C

             reply	other threads:[~2023-02-02 11:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-02 11:29 tlaronde [this message]
2023-02-02 16:50 ` [edk2-devel] edk2setup.sh shortcomings Gerd Hoffmann
2023-02-02 17:59   ` tlaronde
2023-02-02 21:49     ` Brian J. Johnson
2023-02-02 23:06       ` Rebecca Cran
2023-02-03 10:02         ` Marvin Häuser
2023-02-03 12:29         ` tlaronde

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=Y9uenIaO7PuG04pi@polynum.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