Releases: Olf0/crypto-sdcard
v1.3.1-4.sfos340regular
Changes:
- Reintegrated the "sbj edition"'s git repository into this one as branch qcrypto, as they shared most of their content and a workflow to support multiple release branches was established here.
Renamed the "sbj edition" to "qcrypto edition" and the generic edition to "regular edition".
Note that RPMs distributed at OpenRepos will still be uploaded and shown on their specific page for the regular edition and the qcrypto edition; technically they always end(ed) up in the same repository there, anyway. - The release version now consists of two fields, separated by a dot ("."):
- The first field must contain a natural number greater than zero.
This number may be prefixed by one of {alpha,beta,stable}, e.g. "alpha13". - The second field indicates the minimal required SailfishOS version A.B.C.X in the format "sfosABC"; the fourth field of a SailfishOS version ("X") is neither depended upon or denoted.
A single, additional word out of {regular,qcrypto} is directly appended, resulting in the whole second field containing e.g., "sfosABCregular".
- The first field must contain a natural number greater than zero.
v1.3.1-4.sfos340qcrypto
See release notes for v1.3.1-4.sfos340regular.
v1.3.1-4.sfos321regular
See release notes for v1.3.1-4.sfos340regular.
v1.3.1-4.sfos321qcrypto
See release notes for v1.3.1-4.sfos340regular.
v1.3.1-1.sfos340
Changes:
- All changes from v1.3.1-1.sfos321
- Additionally: Adapted to SailfishOS 3.4.0., which moved
systemd-escape
from/bin
to/usr/bin
1.3.1-1.sfos321
Changes:
- Mounting is now restricted to users, who belong to the Unix group media_rw (before, group: system), which is the case for the user nemo since some SailfishOS release before v3.2.1 and after v2.2.1 (unable to assess which one), or the defaultuser on freshly installed devices (since SailfishOS 3.4.0).
Background: The group system is omitted and replaced by sailfish-system in SailfishOS 3.4.0. But as the long extant group media_rw became populated and is a much better fit for this purpose, switch to using that. - Altered versioning scheme, git tags naming and archive file (tarball) names, again; this time to accommodate for multiple release variants per version in order to serve different SailfishOS releases from one repository easily.
- Name and version scheme (three digit semantic versioning) are retained, only the release string format is expanded.
- But the release string is included in the git tags for releases and consequently in the names of their tarballs, again. This is a requirement to support mutually exclusive (by RPM dependencies) releases from different release branches of a single git repository and to publish them altogether in a single RPM repository.
- The release version now consists of two fields, separated by a dot ("."). The new, second field indicates the minimal required SailfishOS version A.B.C.X in the format "sfosABC"; the fourth field of a SailfishOS version ("X") is neither depended upon or denoted.
v1.2.5
v1.2.4
Changes:
- Rectifying and enhancing an incorrect comment WRT the "Icon:" tag, introduced with v1.2.3.
(No icon path, just a pure basename makes sense in the SOURCE directory, because the dirname of an icon path is always stripped byrpmbuild
.) - Introducing a single, fail-safer formatting, to avoid such testing mishap (resulting in a "false positive") in the future.
- Better documenting what is really going on by enhancing the principal "icon comment".
No change in functionality compared to v1.2.3.
v1.2.3
Change:
After researching if there are additional, reasonable mount options for (partitions on) SD-cards, which was triggered by OMP's suggestion at git.sailfishos.org to mount SD-cards with noexec (which makes sense for unencrypted partitions), ultimately adding only lazytime.
Note that the mount option async should already be set as Linux (kernel) default (as sync is deadly for FLASH-based mass storage devices), diratime should be set as Linux default (which is O.K. and reasonable), plus nosuid, nodev and relatime are set by SailfishOS for (partitions on) SD-cards (which are fine).
v1.2.2
Change:
Switch embedded icon from 128 px² to 256 px² in order to accommodate modern hi-res displays.
... and embed a GIF (v89a) icon in RPMs, but never in XPM (v3) file format!
Background:
XPM is absolutely antiquated (it translates a picture in characters!), results in large file sizes (no built-in compression) and of lower image quality than GIF (though both are "8 bit colour palette plus transparency, with 24 bit colours" formats).
GIF89a is technically much more modern than XPMv3 and rpmbuild
only accepts GIF and XPM icons!