You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
zopen-compute-builddeps takes a bit of a sledge hammer approach to computing what tools are actually required to build a particular package.
For example, if I want to determine what tools are required for git to be built, I can say:
zopen-compute-builddeps git
The tool clones the various tools into a temp directory, looks at the ZOPEN_TARBALL_DEPS line and computes the transitive closure of the tools required, and eventually spits out:
Transitive closure of build dependencies for git:
rsync
git
cmake
automake
help2man
texinfo
gettext
xz
perl
diffutils
zoslib
libpcre
bash
make
coreutils
grep
gawk
tar
m4
zlib
expat
autoconf
wget
gzip
curl
ncurses
findutils
openssl
sed
It probably has some bugs and certainly could be improved if someone is interested.
referenceThis discussion is 'complete' but not closed so it can be referenced
1 participant
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
zopen-compute-builddeps takes a bit of a sledge hammer approach to computing what tools are actually required to build a particular package.
For example, if I want to determine what tools are required for git to be built, I can say:
The tool clones the various tools into a temp directory, looks at the ZOPEN_TARBALL_DEPS line and computes the transitive closure of the tools required, and eventually spits out:
It probably has some bugs and certainly could be improved if someone is interested.
Beta Was this translation helpful? Give feedback.
All reactions