| Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
slackrepo tracks the build number, so it should not be bumped by hand
here. Reverts the bump made alongside the directory permission fix; that
fix itself is unchanged.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
|
|
Upstream ships its top directory as 0700. The standard SBo perm-normalize
block only remaps the modes it enumerates (777/775/750/711/555/511 and
the 6xx/4xx file set), so 0700 passed through untouched and the whole
tree installed root-only. Launching as a normal user died with
"Permission denied" on the binary.
Normalize every directory to 755 explicitly, before the chrome-sandbox
chmod so the setuid bit is unaffected. BUILD bumped so the fixed package
supersedes the broken one.
Worth noting for other repacks: neither sbopkglint nor a container build
catches this, both run as root, where 0700 is traversable. Verified here
by extracting the package as a normal user and launching the real binary.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
|
|
Was /opt/Typora-linux-x64 (upstream's own unversioned name), now
/opt/typora-bin-$VERSION, matching kitty-bin and the rest of the repo.
Upgrades can no longer leave a previous release's files behind.
The versioned path is now generated rather than written down twice: the
wrapper ships an @APPDIR@ placeholder that the SlackBuild substitutes,
and the chrome-sandbox setuid line is appended to doinst.sh at build
time. Both would otherwise be stale-version traps on the next bump, the
doinst.sh one silently costing the sandbox its setuid bit.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
|
|
Binary repack of upstream's official Linux x86_64 tarball; Typora is
closed source, so this is not a build from source.
Uses the versioned tarball on downloads.typora.io rather than the
version-agnostic Typora-linux-x64.tar.gz, which serves whatever build is
current and would go md5-stale on every upstream release.
Launch through a wrapper instead of a symlink to the binary: it enables
Electron's Ozone Wayland backend when a Wayland session is detected and
leaves the X11 default alone otherwise, so one package works in both.
Override with TYPORA_OZONE=wayland|x11.
Upstream's bundled updater is dropped; it would overwrite the tree in
/opt behind pkgtool's back.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
|
|
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
|
|
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
|
|
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
|
|
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
|
|
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
|
|
The research doc concluded that getting xe into the initrd was the gate for
the whole splash effort. That holds for SBo 22.02.122, which has no SimpleDRM
support at all, but upstream added it in 24.004.60 and uses it by default on
UEFI to draw on the EFI framebuffer. On this machine that removes the
prerequisite entirely, along with the firmware bloat and the per-kernel-update
maintenance it implied.
Also record that stage 1 is done and verified after reboot: the printk wall is
gone, the rc script wall is not, which no kernel flag can fix. Add a section
answering whether the boot text stays reachable behind a splash (Esc toggles
it, and plymouth does its own console redirection).
Replace the unreadable LQ thread with the Arch wiki as the reference, and note
the repo README that plymouth is -current only.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
|
|
SBo ships 22.02.122, four years behind upstream and predating SimpleDRM
support. Written from the meson template rather than bumped, since upstream
switched from autotools to meson.
systemd-integration now defaults to true in meson and has to be disabled
explicitly, and release-file defaults to /etc/system-release. All build deps
are satisfied by stock -current, so REQUIRES is empty.
-current only: PANGO_ATTR_FONT_SCALE needs pango >= 1.50 and 15.0 ships
1.48.11, so label-pango fails to compile there.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
|
|
Covers how mainstream distros implement boot splash (Plymouth from
initramfs, not kernel patches), the two SBo packages available, and a
two-stage plan for this machine.
Key finding: xe.ko is absent from the current initrd, so there is no
DRM device during the initrd phase and no surface for Plymouth to draw
on. That is the prerequisite for everything else.
Nothing installed or changed; research only.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The SlackBuild calls python3 -m build and python3 -m installer directly,
so both belong in REQUIRES even though hatchling's dep chain already
pulls them in transitively on 15.0 (via python3-editables and
python3-wheel). Declaring them keeps the .info correct if that chain
ever changes.
Rebuilt clean on -current and 15.0.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
|
|
Record that ~/Templates/SlackBuilds/ holds the official SBo templates,
that update-templates.sh refreshes them, and that they are the starting
point for new SlackBuilds and SBo maintenance takeovers.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
|
|
Telegram client library for Python 3.
Built from the codeberg tag archive rather than the PyPI sdist: the sdist
omits telethon_generator/, which the hatch build hook imports to generate
the tl/ layer, so a source build of it always fails.
Tested on -current and 15.0. 15.0 additionally needs python3-hatchling
(-current ships it in base) and the PYTHONPATH=/opt/python$PYVER line for
SBo's -opt packaging/setuptools.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|