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
Next revisionBoth sides next revision
download:sac2c [2019/10/17 14:06] – extend description to better explain basic and full packages... hnvdownload:sac2c [2019/10/17 14:36] – extend description again, include version info hnv
Line 1: Line 1:
 ===== 1 Compiler: the sac2c ecosystem ===== ===== 1 Compiler: the sac2c ecosystem =====
  
-Binary releases of the compiler and the standard library are provided in the following sections.+Binary releases of the compiler and the standard library are provided in the following sections. We provide two release types, major releases and weekly releases.
  
-We provide two types of distributable packagesstable releases and bleeding-edge releases (which we call //weeklies//)In both types, we provide a **basic** and a **full** package.+<callout type="primary" icon="true"> 
 +=== Which release type should I use? === 
 +At the moment, we suggest using one of the //weekly// release packages as these include some of the latest featuresThese packages only differ from our stable release packages in that we do less testing before releasing them. 
 +</callout> 
 + 
 +=== Package Variants ===
  
-////+We provide two types of packages variants, **basic** and  **full**.
  
 <HTML> <HTML>
Line 20: Line 25:
  
 //We use a CI cluster to build these packages using configurations defined in our [[https://www.macs.hw.ac.uk/gitlab/sac-group/build-sac-pkgs|package build repo]].// //We use a CI cluster to build these packages using configurations defined in our [[https://www.macs.hw.ac.uk/gitlab/sac-group/build-sac-pkgs|package build repo]].//
- 
-<callout type="primary" icon="true"> 
-=== Which package should I use? === 
-At the moment, we suggest using one of the //weekly// packages as these include some of the latest features. These packages only differ from our stable release packages in that we do less testing before releasing them. 
-</callout> 
  
 <callout type="primary" icon="true"> <callout type="primary" icon="true">
Line 30: Line 30:
 For normal usage, the **basic** variant is sufficient to try out all of the features of the Single Assignment C language. For normal usage, the **basic** variant is sufficient to try out all of the features of the Single Assignment C language.
 </callout> </callout>
 +
 +=== Version Number ===
 +
 +We use semantic versioning, but additionally store the commit count (since the last version change) and the release number. Using ''1.3.2-256-1'' as an example, ''1.3.2'' is the version number which has ''256'' new commits on top and has been packages/release only once (''1'').
 +
 +//The version number may not match with what is in the filename of the package.//
  
 ==== Weeklies --- Bleeding-Edge Release ==== ==== Weeklies --- Bleeding-Edge Release ====