[Rpm-maint] [rpm-software-management/rpm] Export build script environment information to a well known location (PR #4026)

[Panu Matilainen]

pmatilai left a comment (rpm-software-management/rpm#4026)

Oh, doh. The environment info is *not* currently visible anywhere at all, and somehow I thought it was. Mixed it up with the CFLAGS etc dump that you get from building other stuff.  Tired eyes and stuff :laughing: 

So that not being the case, moving the sourcing before set -x is the obvious thing to do. But, then we could actually improve this thing as well by outputting the environment, just once. It seems at least as important as a whole lot of other goo we output when building :smile: 

For example (dumping this is trivial when creating the file):
```
Executing(%mkbuilddir): /bin/sh -e /var/tmp/rpm-tmp.s63tN6
Build environment:

  RPM_SOURCE_DIR="/home/pmatilai/rpmbuild/SOURCES"
  RPM_BUILD_DIR="/home/pmatilai/rpmbuild/BUILD/popt-1.19-build"
  RPM_OPT_FLAGS="-O2 -g"
  RPM_LD_FLAGS=""
  RPM_ARCH="x86_64"
  RPM_OS="linux"
  RPM_BUILD_NCPUS="8"
  RPM_SPECPARTS_DIR="/home/pmatilai/rpmbuild/BUILD/popt-1.19-build/SPECPARTS"
  export RPM_SOURCE_DIR RPM_BUILD_DIR RPM_OPT_FLAGS RPM_ARCH RPM_OS RPM_BUILD_NCPUS RPM_SPECPARTS_DIR RPM_LD_FLAGS
  RPM_DOC_DIR="/usr/share/doc"
  export RPM_DOC_DIR
  RPM_PACKAGE_NAME="popt"
  RPM_PACKAGE_VERSION="1.19"
  RPM_PACKAGE_RELEASE="7"
[...]
```

-- 
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/4026#issuecomment-3490443610
You are receiving this because you are subscribed to this thread.

Message ID: <rpm-software-management/rpm/pull/4026/c3490443610 at github.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rpm.org/pipermail/rpm-maint/attachments/20251105/19662263/attachment.htm>