Skip to content

amipkg 0.7.4

Choose a tag to compare

@thomas-luebker thomas-luebker released this 30 Jul 08:40

amipkg 0.7.4 — update one package, and install into system drawers properly

Update a single package from the GUI

Both GUIs had Update All but no way to update just one thing — even though
the CLI has taken amipkg upgrade <id> all along. There is now an Update
button beside Update All (and Package → Update, shortcut G).

It is only active when there is genuinely something to do, and the same check
marks the list: outdated packages now show UPDATE in the status column
instead of a flat "installed", so you can see what is worth acting on without
running Check Updates first.

(A package you adopted whose version could not be detected never claims a
false update — an unknown version is not treated as outdated.)

Installing into C:, LIBS:, DEVS: … now does the right thing

Point a package at a system drawer and, until now, the whole archive tree went
there — documentation and all. Worse, an archive that brings its own top drawer
landed nested, so a command installed to C: ended up at C:Tool/Tool, where
the shell will never find it.

System drawers hold flat, specific things, so that is what amipkg does now:

  • programs go in flatC:Tool, not C:Tool/Tool
  • everything else goes beside them, in <install drawer>/<id>, with its
    structure intact

What belongs there is deliberately careful: name conventions first
(.library, .device, .class, .font, .prefs) and the executable header
for the drawers that hold plain commands. Anything unrecognised goes to the
companion drawer, where it does no harm. Both halves are recorded, so remove
still cleans up either way, and amipkg tells you how the split went.

Nothing changes for ordinary app drawers. Installing into SYS:Programs
what almost everything does — behaves exactly as before. This only engages when
you deliberately choose a system drawer, which pairs with the per-package
install drawer from 0.7.2:

amipkg install <id> DIR=C:

Also fixed

Three internal buffers were still sized for the short AMIPKG: prefix although
the resolved path has been absolute since 0.4.7 — on a machine with a long
install path that could have silently truncated a receipt or config path.

Upgrading

amipkg upgrade

Thanks again to yelworC and djbase, whose reports drove most of 0.7.x.