About Basilisk updates
Posted: 2017-12-02, 09:10
As some of you may have realized, Basilisk updates are automatic (by default) and the browser will automatically update itself. This doesn't necessarily get announced on the forum or elsewhere, because Basilisk will be generally be considered a "rolling release" type of application. Internally we do keep some milestone goals to solve bugs against, for proper prioritization of issues, but that doesn't necessarily translate 1:1 to publications.
Published builds will have source snapshots available on the Pale Moon archive server as of 2021-09-27.
Therefore, if you plan to maintain a package distro for Linux, use the basilisk-YYYY.MM.DD-source.tar.xz archives to build from source corresponding to the release date, and make sure to disable the internal updater if you plan to use a system package manager/repository to provide updates. Binary redistribution in unaltered form on Linux is also an option, but be aware that updates will not work unless you have installed Basilisk in a user-writable location.
Older releases will be tagged in the archived source repository with "vYYYY.MM.DD" and indicated in our release notes on http://www.basilisk-browser.org/releasenotes.shtml.
Published builds will have source snapshots available on the Pale Moon archive server as of 2021-09-27.
Therefore, if you plan to maintain a package distro for Linux, use the basilisk-YYYY.MM.DD-source.tar.xz archives to build from source corresponding to the release date, and make sure to disable the internal updater if you plan to use a system package manager/repository to provide updates. Binary redistribution in unaltered form on Linux is also an option, but be aware that updates will not work unless you have installed Basilisk in a user-writable location.
Older releases will be tagged in the archived source repository with "vYYYY.MM.DD" and indicated in our release notes on http://www.basilisk-browser.org/releasenotes.shtml.