HyperWiki

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision 		Previous revision
en:project:update_philosophy [2024/04/05 00:19]
throgh [Example #1: Issues for liblzma] 		en:project:update_philosophy [2024/04/05 13:25] (current)
throgh [Example #2: Using GCC-8 for HyperbolaBSD]
Line 28: Line 28:
  
 ===== Example #2: Using GCC-8 for HyperbolaBSD ===== ===== Example #2: Using GCC-8 for HyperbolaBSD =====
 +
 +We have mentioned before that we follow the approach to optimize our packages with every new released version and this includes also our implemented compilers and environments for programming. For **HyperbolaBSD** we surely want to use newer standards alike [[https://en.wikipedia.org/wiki/C17_(C_standard_revision)|C17 (gnu17)]].
 +
 +The reasoning is the same as mentioned before: Minimalism but also the focus on clear and clean code. When a software is running likewise fine with the used environment, foremost free from errors, it is also quite more easy to focus on later updates, including enumerating and evaluating possible problems. Following only the paradigm to "upgrade fast and without compromises" this ends always in unseen spots, which later surely get hold in severe errors and bugs.
 +
 +Our pre-alpha nevertheless will follow first the approach to use GCC-4 with [[https://en.wikipedia.org/wiki/C99|C99]] as base. Therefore you can also see the progression within as said the following up development for further releases will conclude as said in usage of GCC-8 and the migration of the working code-base established throughout C99 first.
 +===== Conclusion =====
 +
 +Withing this article we have explained more in detail why Hyperbola as system-project do not want to follow the principle for inclusion "always the newest releases". Besides this is also no promise for more security ([[https://wiki.hyperbola.info/doku.php?id=en:project:update_philosophy#example_1issues_for_liblzma|Example #1]]) we can also conclude that this would risk the stability of our system and further development: Knowing the dependencies, understanding the system and working out a good, secure development. The lesser, the better and cleaner!