Repository navigation
omapass 0.1.47
Fixed
-
install.shanduninstall.shno longer delete another plugin that happens
to use the bareomapassid. That id was ours until 0.1.12 namespaced it to
cschaba.omapass, so~/.config/omarchy/plugins/omapasswas treated as an
old install of ours and cleared away — and it is another plugin's address
now: tonyrumans/omapass declaresomapassas its plugin id and
installs exactly there. Anyone with both would have lost theirs, silently, to
a message claiming OmaPass had tidied up after itself.Both scripts now read the manifest in that directory before touching it. Only
a manifest that is recognisably ours — the namespaced id, our homepage, or
Omapass.qmlas the overlay entry point, which every version we have
shipped declares — is removed or disabled. Anything else is named and left
alone, and OmaPass installs alongside it under its own id. A directory with
no manifest at all is still ours: it predates the plugin contract.The rule fails closed, because the costs are not symmetric. Leaving a stale
directory of ours behind is untidy; deleting a working install of somebody
else's is not something a password manager gets to do twice. ([#44])
Install
omarchy plugin add https://github.com/cschaba/omapass.git --enable --yesOr from the tarball below:
tar -xzf omapass-0.1.47.tar.gz
cd omapass-0.1.47 && ./install.shsha256: 5b07debbee61f03f3600b2875032d864c0fc989061707433cda0703d9ad98d62
Under development and largely untested — see the warning at the top
of the README before trusting it with anything.