buninu-linux 0.2.0

package/initramfs/buninu/apps/bunmsh/test/t.sh

@@ -0,0 +1,12 @@
+#!/bin/sh
+
+echo shell-before
+Bun.version
+Bun.e, Math.cos(1)
+
+Bun.sha.var = { message: "shared", count: 1 }
+Bun.sha.var.count += 1
+Bun.sha.var
+echo "from command substitution: $(Bun.sha.var.message)"
+
+echo shell-after

package/initramfs/buninu/apps/bunx/bunx.js

@@ -0,0 +1,172 @@
+#!/usr/bin/env bun
+
+// bunx <package>[@version] [args...]
+//
+// Buninu's own bunx: ensures <package> is globally installed via `bun i -g`,
+// then execs the matching ~/.bun/bin/<binary> directly, forwarding the
+// remaining arguments. Registered in apps/cmdlist like any other Buninu
+// command; whether it actually shadows the real `bunx` (Bun's own
+// ephemeral-run subcommand) depends on whether Buninu's bin/ comes before it
+// in PATH -- Buninu appends its bin/ to the inherited PATH rather than
+// prepending it, so an already-installed bun's own bunx will normally still
+// win unless this one is invoked some other way.
+//
+// The "when do we reinstall" rules below are ported from real bunx's own
+// decision tree (src/runtime/cli/bunx_command.rs in the Bun source tree),
+// adapted from its private per-version cache to this script's single shared
+// `bun i -g` install:
+//   - an explicit dist-tag (e.g. "latest", "next") never reuses a cached
+//     binary -- real bunx sets look_for_existing_bin = false for that case
+//     and always resolves fresh.
+//   - a missing binary always installs.
+//   - an explicit pinned/ranged version reinstalls if bun's own global
+//     install record (install/global/package.json) doesn't already list
+//     that same version string for this package -- there is no equivalent
+//     check in real bunx because its cache is already keyed by version; this
+//     is this script's substitute, since `bun i -g` overwrites one shared
+//     path regardless of version.
+//   - otherwise, reinstall once the binary is older than 24h
+//     (SECONDS_CACHE_VALID in bunx_command.rs), or if it can't be stat'd at
+//     all -- real bunx also treats a stat failure as stale.
+
+const fs = require("fs");
+const path = require("path");
+
+const CACHE_TTL_MS = 24 * 60 * 60 * 1000; // matches real bunx's SECONDS_CACHE_VALID
+
+function fail(message) {
+  console.error(`bunx: ${message}`);
+  process.exit(1);
+}
+
+// Split "@scope/name@version" (or unscoped variants) into name/version/pkgName.
+// version is "" when the spec didn't include one.
+function parseSpec(spec) {
+  let rest = spec;
+  let scope = "";
+  if (rest.startsWith("@")) {
+    const slash = rest.indexOf("/");
+    if (slash === -1) fail(`invalid package spec: ${spec}`);
+    scope = rest.slice(0, slash);
+    rest = rest.slice(slash + 1);
+  }
+  const at = rest.lastIndexOf("@");
+  const name = at === -1 ? rest : rest.slice(0, at);
+  const version = at === -1 ? "" : rest.slice(at + 1);
+  return { name, version, pkgName: scope ? `${scope}/${name}` : name };
+}
+
+// A bare word like "latest"/"next"/"beta"/"canary" is an npm dist-tag.
+// Anything starting with a digit, "v", or a range operator is treated as a
+// real pinned version/range instead.
+function isDistTag(version) {
+  return !/^[vV]?\d|^[\^~<>=]/.test(version);
+}
+
+// Ask bun itself where its global bin dir is, rather than re-deriving
+// $BUN_INSTALL/$HOME ourselves -- this is the same resolution bun's own
+// installer used, so it can't disagree with where `bun i -g` actually put
+// things (config file settings included, not just env vars).
+//
+// `bun pm bin -g` only works once something has been globally installed at
+// least once (it errors with "no package.json" for install/global before
+// that project exists). On a fresh $BUN_INSTALL/$HOME this script hasn't
+// installed anything yet either, so fall back to the plain env-var
+// computation for that first call -- needsInstall() below will see nothing
+// at that path and install, which creates the project bun pm needs, so every
+// call after the first one resolves through bun pm bin -g instead.
+function globalBinDir() {
+  const result = Bun.spawnSync(["bun", "pm", "bin", "-g"], {
+    stdio: ["ignore", "pipe", "ignore"],
+  });
+  if (result.exitCode === 0) return result.stdout.toString().trim();
+  return path.join(process.env.BUN_INSTALL || path.join(process.env.HOME, ".bun"), "bin");
+}
+
+// `bun i -g` produces bin/<name> on POSIX (a relative symlink resolved via
+// shebang) but bin/<name>.exe on Windows (a compiled shim + a companion
+// .bunx metadata file -- Windows has neither reliable symlinks nor shebang
+// support). Missing this suffix means every Windows lookup below finds
+// nothing, which is harmless: needsInstall() just treats it as "not
+// installed on this platform yet" and installs it here.
+const EXE_SUFFIX = process.platform === "win32" ? ".exe" : "";
+
+// Buninu on Android isn't actually running inside Termux, so nothing sets
+// $PREFIX -- but some installed CLIs check it at runtime to find themselves
+// relative to a Termux/Android system. Fake it only for the actual target
+// execution below (not the `bun i -g` install step); an existing $PREFIX
+// (e.g. genuinely running under Termux) is left alone.
+function childEnv() {
+  if (process.platform !== "android" || process.env.PREFIX) return process.env;
+  return { ...process.env, PREFIX: "/data/data/com.termux/files/usr" };
+}
+
+function recordedVersion(bunInstallRoot, pkgName) {
+  const manifestPath = path.join(bunInstallRoot, "install", "global", "package.json");
+  try {
+    const manifest = JSON.parse(fs.readFileSync(manifestPath, "utf8"));
+    return manifest.dependencies && manifest.dependencies[pkgName];
+  } catch {
+    return undefined;
+  }
+}
+
+function needsInstall(bunInstallRoot, target, version, pkgName) {
+  if (version && isDistTag(version)) return true;
+  if (!fs.existsSync(target)) return true;
+  if (version && recordedVersion(bunInstallRoot, pkgName) !== version) return true;
+  try {
+    const age = Date.now() - fs.statSync(target).mtimeMs;
+    return age > CACHE_TTL_MS;
+  } catch {
+    return true;
+  }
+}
+
+const args = process.argv.slice(2);
+if (args.length < 1) fail("usage: bunx <package>[@version] [args...]");
+
+const spec = args[0];
+const forwarded = args.slice(1);
+const { name: bin, version, pkgName } = parseSpec(spec);
+const binDir = globalBinDir();
+const bunInstallRoot = path.dirname(binDir);
+const target = path.join(binDir, bin + EXE_SUFFIX);
+
+if (needsInstall(bunInstallRoot, target, version, pkgName)) {
+  // Same Android check bin/init.js's detectEnvironment() uses. Android's
+  // storage (FUSE-backed app-private paths) frequently rejects hardlinks
+  // and symlinks across the directories bun links between, so fall back to
+  // plain file copies there; hardlink (bun's default) is fine elsewhere.
+  const installArgs = ["bun", "i", "-g", spec];
+  if (fs.existsSync("/system/bin/linker64")) installArgs.push("--backend=copyfile");
+
+  const install = Bun.spawnSync(installArgs, {
+    stdio: ["inherit", "inherit", "inherit"],
+  });
+  
+  // Don't check exit code so even if
+  // bun install killed by SIGSYS @issue #39060
+  // bunx still runs with actually existing bin
+  //if (install.exitCode !== 0) process.exit(install.exitCode ?? 1);
+}
+
+if (!fs.existsSync(target)) {
+  fail(`${spec} installed but ${target} not found (binary name may differ from package name)`);
+}
+
+// Run through `bun <target>` instead of exec'ing `target` directly. Real
+// bunx does the latter (relies on the OS reading the shebang), which is fine
+// on desktop but not reliable here: on Android the resolved bin usually
+// lives under a path mounted noexec, so the kernel refuses to exec it even
+// though it's readable and chmod +x. `bun` itself is the one binary Android
+// does let us execute (from nativeLibraryDir), so hand it the target as an
+// argument to read+run rather than exec directly. Trade-off: a package whose
+// "bin" is a real native executable (not a JS/bun script) won't run this
+// way -- accepted, since that's the rarer case and this is what makes the
+// common (JS-script bin) case work on Android at all.
+const run = Bun.spawnSync(["bun", target, ...forwarded], {
+  env: childEnv(),
+  stdio: ["inherit", "inherit", "inherit"],
+});
+process.exit(run.exitCode ?? 1);

package/initramfs/buninu/apps/cmdlist

@@ -0,0 +1,48 @@
+# syntax: markdown
+
+### glow — Render files with jsmdcui syntax highlighting
+glow
+
+### jmi — Open files in the js micro editor
+jmi
+
+### jsgotty — Run a browser-accessible terminal
+jsgotty
+
+### jsmdcui — Edit and run interactive Markdown applications
+jsmdcui
+
+### musl-la — Launch AArch64 ELF programs with the bundled musl loader
+musl-la
+
+### buninu-help — Render README.md with glow, then show icon.png with jsgotty --viu
+buninu-help
+
+### bunx — Globally install a package with bun, then exec its matching binary
+bunx
+
+### native-bridge — Call the Android host app (toast, clipboard) over PKG_BRIDGE_SOCK; bare invocation lists what the host implements
+native-bridge
+
+### xclip — X11-style clipboard tool; -selection clipboard/-clip bridges to the real Android clipboard via native-bridge
+xclip
+
+### tts — Speak text through the Android host and wait for it to finish (-a to not wait)
+tts
+
+### showimg — Shorthand for jsgotty --viu
+showimg
+
+### rz — Upload a file over ZMODEM (bun apps/jsgotty/rz.js)
+rz
+
+### sz — Download a file over ZMODEM (bun apps/jsgotty/sz.js)
+sz
+
+### xdg-open — Open a file or URL with the platform's default handler (native bridge on Android, open/start/xdg-open elsewhere) '
+xdg-open
+
+
+### bunmsh – Bun Modern Shell
+
+bunmsh

package/initramfs/buninu/apps/jsgotty/LICENSE

@@ -0,0 +1,23 @@
+MIT License
+
+Copyright (c) 2015-2017 Iwasaki Yudai
+Copyright (c) 2021-2022 Søren L. Hansen
+Copyright (c) 2026 Dr. John(醫者小智)
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/initramfs/buninu/apps/jsgotty/LICENSES/Apache-2.0-zmodem.js.txt

@@ -0,0 +1,201 @@
+Apache License
+Version 2.0, January 2004
+http://www.apache.org/licenses/
+
+TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+1. Definitions.
+
+"License" shall mean the terms and conditions for use, reproduction,
+and distribution as defined by Sections 1 through 9 of this document.
+
+"Licensor" shall mean the copyright owner or entity authorized by
+the copyright owner that is granting the License.
+
+"Legal Entity" shall mean the union of the acting entity and all
+other entities that control, are controlled by, or are under common
+control with that entity. For the purposes of this definition,
+"control" means (i) the power, direct or indirect, to cause the
+direction or management of such entity, whether by contract or
+otherwise, or (ii) ownership of fifty percent (50%) or more of the
+outstanding shares, or (iii) beneficial ownership of such entity.
+
+"You" (or "Your") shall mean an individual or Legal Entity
+exercising permissions granted by this License.
+
+"Source" form shall mean the preferred form for making modifications,
+including but not limited to software source code, documentation
+source, and configuration files.
+
+"Object" form shall mean any form resulting from mechanical
+transformation or translation of a Source form, including but
+not limited to compiled object code, generated documentation,
+and conversions to other media types.
+
+"Work" shall mean the work of authorship, whether in Source or
+Object form, made available under the License, as indicated by a
+copyright notice that is included in or attached to the work
+(an example is provided in the Appendix below).
+
+"Derivative Works" shall mean any work, whether in Source or Object
+form, that is based on (or derived from) the Work and for which the
+editorial revisions, annotations, elaborations, or other modifications
+represent, as a whole, an original work of authorship. For the purposes
+of this License, Derivative Works shall not include works that remain
+separable from, or merely link (or bind by name) to the interfaces of,
+the Work and Derivative Works thereof.
+
+"Contribution" shall mean any work of authorship, including
+the original version of the Work and any modifications or additions
+to that Work or Derivative Works thereof, that is intentionally
+submitted to Licensor for inclusion in the Work by the copyright owner
+or by an individual or Legal Entity authorized to submit on behalf of
+the copyright owner. For the purposes of this definition, "submitted"
+means any form of electronic, verbal, or written communication sent
+to the Licensor or its representatives, including but not limited to
+communication on electronic mailing lists, source code control systems,
+and issue tracking systems that are managed by, or on behalf of, the
+Licensor for the purpose of discussing and improving the Work, but
+excluding communication that is conspicuously marked or otherwise
+designated in writing by the copyright owner as "Not a Contribution."
+
+"Contributor" shall mean Licensor and any individual or Legal Entity
+on behalf of whom a Contribution has been received by Licensor and
+subsequently incorporated within the Work.
+
+2. Grant of Copyright License. Subject to the terms and conditions of
+this License, each Contributor hereby grants to You a perpetual,
+worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+copyright license to reproduce, prepare Derivative Works of,
+publicly display, publicly perform, sublicense, and distribute the
+Work and such Derivative Works in Source or Object form.
+
+3. Grant of Patent License. Subject to the terms and conditions of
+this License, each Contributor hereby grants to You a perpetual,
+worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+(except as stated in this section) patent license to make, have made,
+use, offer to sell, sell, import, and otherwise transfer the Work,
+where such license applies only to those patent claims licensable
+by such Contributor that are necessarily infringed by their
+Contribution(s) alone or by combination of their Contribution(s)
+with the Work to which such Contribution(s) was submitted. If You
+institute patent litigation against any entity (including a
+cross-claim or counterclaim in a lawsuit) alleging that the Work
+or a Contribution incorporated within the Work constitutes direct
+or contributory patent infringement, then any patent licenses
+granted to You under this License for that Work shall terminate
+as of the date such litigation is filed.
+
+4. Redistribution. You may reproduce and distribute copies of the
+Work or Derivative Works thereof in any medium, with or without
+modifications, and in Source or Object form, provided that You
+meet the following conditions:
+
+(a) You must give any other recipients of the Work or
+Derivative Works a copy of this License; and
+
+(b) You must cause any modified files to carry prominent notices
+stating that You changed the files; and
+
+(c) You must retain, in the Source form of any Derivative Works
+that You distribute, all copyright, patent, trademark, and
+attribution notices from the Source form of the Work,
+excluding those notices that do not pertain to any part of
+the Derivative Works; and
+
+(d) If the Work includes a "NOTICE" text file as part of its
+distribution, then any Derivative Works that You distribute must
+include a readable copy of the attribution notices contained
+within such NOTICE file, excluding those notices that do not
+pertain to any part of the Derivative Works, in at least one
+of the following places: within a NOTICE text file distributed
+as part of the Derivative Works; within the Source form or
+documentation, if provided along with the Derivative Works; or,
+within a display generated by the Derivative Works, if and
+wherever such third-party notices normally appear. The contents
+of the NOTICE file are for informational purposes only and
+do not modify the License. You may add Your own attribution
+notices within Derivative Works that You distribute, alongside
+or as an addendum to the NOTICE text from the Work, provided
+that such additional attribution notices cannot be construed
+as modifying the License.
+
+You may add Your own copyright statement to Your modifications and
+may provide additional or different license terms and conditions
+for use, reproduction, or distribution of Your modifications, or
+for any such Derivative Works as a whole, provided Your use,
+reproduction, and distribution of the Work otherwise complies with
+the conditions stated in this License.
+
+5. Submission of Contributions. Unless You explicitly state otherwise,
+any Contribution intentionally submitted for inclusion in the Work
+by You to the Licensor shall be under the terms and conditions of
+this License, without any additional terms or conditions.
+Notwithstanding the above, nothing herein shall supersede or modify
+the terms of any separate license agreement you may have executed
+with Licensor regarding such Contributions.
+
+6. Trademarks. This License does not grant permission to use the trade
+names, trademarks, service marks, or product names of the Licensor,
+except as required for reasonable and customary use in describing the
+origin of the Work and reproducing the content of the NOTICE file.
+
+7. Disclaimer of Warranty. Unless required by applicable law or
+agreed to in writing, Licensor provides the Work (and each
+Contributor provides its Contributions) on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+implied, including, without limitation, any warranties or conditions
+of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+PARTICULAR PURPOSE. You are solely responsible for determining the
+appropriateness of using or redistributing the Work and assume any
+risks associated with Your exercise of permissions under this License.
+
+8. Limitation of Liability. In no event and under no legal theory,
+whether in tort (including negligence), contract, or otherwise,
+unless required by applicable law (such as deliberate and grossly
+negligent acts) or agreed to in writing, shall any Contributor be
+liable to You for damages, including any direct, indirect, special,
+incidental, or consequential damages of any character arising as a
+result of this License or out of the use or inability to use the
+Work (including but not limited to damages for loss of goodwill,
+work stoppage, computer failure or malfunction, or any and all
+other commercial damages or losses), even if such Contributor
+has been advised of the possibility of such damages.
+
+9. Accepting Warranty or Additional Liability. While redistributing
+the Work or Derivative Works thereof, You may choose to offer,
+and charge a fee for, acceptance of support, warranty, indemnity,
+or other liability obligations and/or rights consistent with this
+License. However, in accepting such obligations, You may act only
+on Your own behalf and on Your sole responsibility, not on behalf
+of any other Contributor, and only if You agree to indemnify,
+defend, and hold each Contributor harmless for any liability
+incurred by, or claims asserted against, such Contributor by reason
+of your accepting any such warranty or additional liability.
+
+END OF TERMS AND CONDITIONS
+
+APPENDIX: How to apply the Apache License to your work.
+
+To apply the Apache License to your work, attach the following
+boilerplate notice, with the fields enclosed by brackets "{}"
+replaced with your own identifying information. (Don't include
+the brackets.) The text should be enclosed in the appropriate
+comment syntax for the file format. We also recommend that a
+file or class name and description of purpose be included on the
+same "printed page" as the copyright notice for easier
+identification within third-party archives.
+
+Copyright {yyyy} {name of copyright owner}
+
+Licensed under the Apache License, Version 2.0 (the "License");
+you may not use this file except in compliance with the License.
+You may obtain a copy of the License at
+
+http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License.

package/initramfs/buninu/apps/jsgotty/NOTICE

@@ -0,0 +1,21 @@
+js-gotty
+Copyright (c) 2015-2017 Iwasaki Yudai
+Copyright (c) 2021-2022 Søren L. Hansen
+Copyright (c) 2026 Dr. John(醫者小智)
+
+This project is licensed under the MIT License. See the LICENSE file in the
+repository root.
+
+This project also redistributes third-party components under their own
+licenses.
+
+Included third-party component:
+
+1. zmodem.js - ZMODEM for JavaScript
+   Copyright 2017 Gasper Software Consulting
+   Licensed under the Apache License, Version 2.0
+   Local copy of license text:
+   LICENSES/Apache-2.0-zmodem.js.txt
+
+The bundled file [static/js/zmodem.js] is byte-for-byte identical to the
+upstream npm release zmodem.js version 0.1.10 dist/zmodem.js.