Congratulations on arriving at the auspicious milestone of the first stable release for the Linux app! I've witnessed first-hand the polishing that's taken place on it and couldn't agree more that it's ready for primetime; all of the minor quibbles that existed when I first started using it have been resolved and now it just "works."
I would like to raise one very trivial concern though regarding the Debian packaging, after just having installed the stable release over the most recent beta, while it's fresh in my mind. I noticed (by way of etckeeper) that the stable package overwrites the
1password.list file in
/etc/apt/sources.list.d so that only the "stable" suite remains. While I can appreciate why you might wish to migrate the early adopters away from the development release channels, making changes to files under /etc (which the FHS 3.0 classifies as the province of the system administrator) without user interaction/confirmation doesn't feel right to me. I can think of a couple different ways the file could be changed as part of the upgrade path more transparently without (I think) being pedantic, and I hope you won't mind me enumerating them here unbidden.
debian/conffilesin the source package. Doing so causes dpkg to hash the file upon install and thereafter when changes are included with subsequent package releases, the user will be prompted to accept or reject them and is offered a diff to inform them of the intended changes. This would also necessitate adding the
1password.listfile to the package contents proper as opposed to the current approach of redirecting stdout to the file from the postinst maintscript.
1password.listfile in the package contents that included a line for each suite but all commented out, so that the user's choices made in debconf would be tied to a shell script function that used some basic "sed-fu" to strip the comment characters from the lines the user wished enabled.
op, whose help output might look like:
... op repo show current repository configuration op repo list list available packages op repo default restore default configuration op repo disable disable repository updates op repo stable make all regular 1Password packages available (default) op repo beta additionally, make feature preview packages available op repo edge additionally, make nightly build packages available
Anyhow, this post is already too long so I'm gonna wrap it up here. I only went into as much details as I did here out of a sense of respect for your time and expertise; I detest being on the receiving end of feature/functionality requests with an implicit expectation that I research the basics of the possible implementations and so tried my best not to do that to you here. Should you want to discuss this further at any point, though, I'm at your disposal through all the usual channels.
1Password Version: 8.1.0
Extension Version: 1.25.7
OS Version: Kubuntu 21.04 (5.11.0-18-generic)
Sync Type: Not Provided