Optimize Installers

Abierto
  • ¿Algo no está bien?
#1,956 2 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
35/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
c
Área
release

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.

Lenguaje dominante
C
Estrellas
11.7k
Forks
1.4k
Merge medio
1 d 1 h
PR fusionados (30 d)
28

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de veracrypt/VeraCrypt

Todos los issues de veracrypt/VeraCrypt

Issues similares

Más issues de C

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.