Update dependencies #2

x7z4w commented 2026年02月05日 19:07:45 +01:00

No description provided.

zyphlar commented 2026年02月05日 20:08:38 +01:00

Why LLVM and not Make? (I can guess but want to ask)

Why LLVM and not Make? (I can guess but want to ask)

x7z4w commented 2026年02月05日 20:14:09 +01:00

@zyphlar wrote in #2 (comment):

Why LLVM and not Make? (I can guess but want to ask)

make was already installed (as the other deps I've removed)
LLVM is for code coverage (probably not needed though, need to check): comaps/comaps@e257534a97/.forgejo/workflows/coverage-check.yaml (L90-89)

@zyphlar wrote in https://codeberg.org/comaps/docker-android-sdk/pulls/2#issuecomment-10394252: > Why LLVM and not Make? (I can guess but want to ask) `make` was already installed (as the other deps I've removed) LLVM is for code coverage (probably not needed though, need to check): https://codeberg.org/comaps/comaps/src/commit/e257534a97c5bd656a350b7820dd8cd071718e27/.forgejo/workflows/coverage-check.yaml#L90-89

zyphlar commented 2026年02月06日 20:17:16 +01:00

I highly prefer listing all dependencies we care about, whether or not they're already installed. It'll take a half-second to output the fact that it's installed, but then later when we're going around running this on some other distro or updating dependencies we aren't forgetting that oh, yeah, XYZ is outdated/deprecated/important/etc.

My top issue with compiling stuff has always been people's assumptions about what's present or missing on a system, and before paying AI 20ドル/mo it'd be easy to waste multiple days just digging through the stack of package names and included packages on i.e. Ubuntu that are different/missing on i.e. Alpine or Arch. I'm currently wading through i.e. not even interesting compilation issues on Windows, just the fact that Python arrives broken on Windows depending on how exactly it's installed, with no obvious error messages or rhyme/reason either way. When I get it working, my docs/scripts will be very opinionated on the right way to install Python so as to save others the headache.

I'd very much appreciate if you re-added the things that we do want to be present, so that the dependency documentation lives in the dependency installation itself, with fewer assumptions.

I highly prefer listing all dependencies we care about, whether or not they're already installed. It'll take a half-second to output the fact that it's installed, but then later when we're going around running this on some other distro or updating dependencies we aren't forgetting that oh, yeah, XYZ is outdated/deprecated/important/etc. My top issue with compiling stuff has always been people's assumptions about what's present or missing on a system, and before paying AI 20ドル/mo it'd be easy to waste multiple days just digging through the stack of package names and included packages on i.e. Ubuntu that are different/missing on i.e. Alpine or Arch. I'm currently wading through i.e. not even interesting compilation issues on Windows, just the fact that Python arrives broken on Windows depending on how exactly it's installed, with no obvious error messages or rhyme/reason either way. When I get it working, my docs/scripts will be very opinionated on the *right* way to install Python so as to save others the headache. I'd very much appreciate if you re-added the things that we do want to be present, so that the dependency documentation lives in the dependency installation itself, with fewer assumptions.

x7z4w commented 2026年02月06日 21:10:55 +01:00

@zyphlar wrote in #2 (comment):

I highly prefer listing all dependencies we care about, whether or not they're already installed. It'll take a half-second to output the fact that it's installed, but then later when we're going around running this on some other distro or updating dependencies we aren't forgetting that oh, yeah, XYZ is outdated/deprecated/important/etc.

My top issue with compiling stuff has always been people's assumptions about what's present or missing on a system, and before paying AI 20ドル/mo it'd be easy to waste multiple days just digging through the stack of package names and included packages on i.e. Ubuntu that are different/missing on i.e. Alpine or Arch. I'm currently wading through i.e. not even interesting compilation issues on Windows, just the fact that Python arrives broken on Windows depending on how exactly it's installed, with no obvious error messages or rhyme/reason either way. When I get it working, my docs/scripts will be very opinionated on the right way to install Python so as to save others the headache.

I'd very much appreciate if you re-added the things that we do want to be present, so that the dependency documentation lives in the dependency installation itself, with fewer assumptions.

We don't use make or zip or even openssh-client in our app anyway.
All the required dependencies are already listed in the main repo's docs, people shouldn't need to check some internal files from a different repo to build the app.

(and TBH how is that related to this PR)?

@zyphlar wrote in https://codeberg.org/comaps/docker-android-sdk/pulls/2#issuecomment-10416648: > I highly prefer listing all dependencies we care about, whether or not they're already installed. It'll take a half-second to output the fact that it's installed, but then later when we're going around running this on some other distro or updating dependencies we aren't forgetting that oh, yeah, XYZ is outdated/deprecated/important/etc. > > My top issue with compiling stuff has always been people's assumptions about what's present or missing on a system, and before paying AI 20ドル/mo it'd be easy to waste multiple days just digging through the stack of package names and included packages on i.e. Ubuntu that are different/missing on i.e. Alpine or Arch. I'm currently wading through i.e. not even interesting compilation issues on Windows, just the fact that Python arrives broken on Windows depending on how exactly it's installed, with no obvious error messages or rhyme/reason either way. When I get it working, my docs/scripts will be very opinionated on the _right_ way to install Python so as to save others the headache. > > I'd very much appreciate if you re-added the things that we do want to be present, so that the dependency documentation lives in the dependency installation itself, with fewer assumptions. We don't use `make` or `zip` or even `openssh-client` in our app anyway. All the required dependencies are already listed in the main repo's docs, people shouldn't need to check some internal files from a different repo to build the app. (and TBH how is that related to this PR)?