Optimize Installers

Open
  • Is something wrong?
#1,956 2 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
c
Domain
release

Research direction

Start by reviewing the Linux package variants, Windows MSI build outputs, website Downloads section, and release bundle packaging. Assess each requested change for compatibility and maintenance impact across supported platforms. Done means deciding which installer and documentation changes are feasible and updating the release artifacts and download listings accordingly.

Written by the indexing model from the issue text.

Description

Hello @idrassi, big thanks for the new version 1.26.30.

VeraCrypt has many installers (Windows, macOS, Linux, and even Raspberry Pi).

The Linux installers are kind of overwhelming, maybe these change could be achieved to avoid redundancy and stop maintaining many files/architectures.

  • The "Console" packages of Debian/Ubuntu and RPM could be deprecated, because the "GUI" already contains the CLI options. The "GUI" packages are like a "superset" of "Console" packages.
  • The 32 bits versions could also be deprecated (like you did for Windows and macOS installers a long time ago). Nowadays, it's very strange to see a 32 bits OS, even for "Minimal"/"Server" Linux distributions. System requirements for Windows and macOS need a modern system, so this could also be applied for Linux.
  • About Windows MSI installers, only if possible, both MSI files (x64 and ARM64) could be merged into a single file; like EXE ("Setup") installer.
  • In the Downloads section of the Main Site (https://veracrypt.jp), you can post the Russian and Chinese versions of the "User Guide CHM". These are only available on Launchpad, they are like "hidden".
  • The "Bundle containing all release files" is a ".7z" format. Maybe the ideal format can be a ZIP file, even if the bundle size would be larger, because it's more compatible across all Operating Systems. If a user wants to have a Bundle, it needs to be easy to extract without requiring to install 7-Zip, WinRAR or PeaZip.

Thanks for your great development.

Dominant language
C
Stars
11.7k
Forks
1.4k
Avg merge
1d 1h
Merged PRs (30d)
28

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from veracrypt/VeraCrypt

All issues in veracrypt/VeraCrypt

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.