BOTCH-MULTIAR...PRETER-PROBLEM(1)

πŸ’– BOTCH-MULTIARCH-INTERPRETER-PROBLEM πŸ’–

okay so bestie, welcome to botch-multiarch-interpreter-problem, a lil tool from the botch tools collection and honestly? it's giving detective energy πŸ”βœ¨


✨ NAME ✨

botch-multiarch-interpreter-problem β€” find all arch:all packages that allow switching architectures πŸ¦‹


🌸 SYNOPSIS 🌸

botch-multiarch-interpreter-problem [-h] [-v] graph.xml

πŸ’… DESCRIPTION πŸ’…

So you hand this program a package graph, and it hands you back a page β€” plain text format, no frills β€” listing every Architecture:all package that is NOT Multi-Arch:foreign and that sits on a dependency path between two Architecture:any packages. no cap, that's the whole gig πŸ‘‘

More precisely (because we love precision in this house πŸ’œ): dose-ceve creates a graph where the nodes are binary packages and source packages, and the edges are their dependency and provides relationships. This program prints all nodes (or packages) that fulfill these criteria:

  • the package is not Multi-Arch:foreign πŸ™…
  • the package is Architecture:all
  • the package has a (possibly transitive) predecessor in the dependency graph that is either an Architecture:any binary package or a source package that builds Architecture:any packages
  • the package has a (possibly transitive) successor in the dependency graph that is Architecture:any and not Multi-Arch:foreign. lowkey important: traversal of the successors stops at Multi-Arch:foreign packages πŸ›‘

πŸŽ€ OPTIONS πŸŽ€

  • -v, --verbose β€” be verbose. spill the tea, tell me everything πŸ—£οΈ
  • -h, --help β€” print help message. the classic cry for help, we've all been there 🫢
  • --packages β€” Packages file to retrieve binary package size πŸ“¦
  • -H, --html β€” output HTML document with additional statistics πŸ“Šβœ¨

🌈 EXAMPLE 🌈

okay so listen, there's a vibe check here and it's important:

The graph created by dose-ceve must not contain Build-Depends-Indep dependencies because source packages do not have to be cross-built to create their Architecture:all packages. These can always be retrieved by native compilation.

Also:

The graph does not have to include builds-from relationships because the Architecture field of source packages is used to determine whether a source package builds Architecture:any binary packages.

Now the actual run, bestie:

dose-ceve --deb-drop-b-d-indep --deb-native-arch=amd64 -G pkg -T grml deb://Packages.gz debsrc://Sources.gz > graph.xml
botch-multiarch-interpreter-problem --packages=Packages.gz graph.xml > out.html
w3m out.html

and boom, you're browsing your own lil html report in w3m πŸ’– (iconic honestly)


πŸ’€ BUGS πŸ’€

See <http://bugs.debian.org/botch>.


πŸ¦‹ SEE ALSO πŸ¦‹

Debian doc-base Manual /usr/share/doc/botch/wiki/Home.html πŸ“–


πŸ‘‘ AUTHOR πŸ‘‘

This man page was written by Johannes Schauer. Botch is written by Johannes Schauer and Pietro Abate. absolute legends, we stan 🫢


Copyright 2012-2014 Johannes Schauer, Pietro Abate

This program is free software: you can redistribute it and/or modify it under the terms of the GNU Lesser General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version. A special linking exception to the GNU Lesser General Public License applies to this library, see the COPYING file for more information. πŸ“œ


and that's the whole page bestie!! this was rendered with perl v5.36.0, dated 2023-02-17, under the manual name BOTCH-MULTIAR...PRETER-PROBLEM(1) from botch tools. go forth and multiarch, periodt πŸ’…βœ¨πŸ¦‹

πŸ“¦ where this page comes from