How to update a GLF-distributed Linux distribution from one release version to the next      20221214 GLF
----------------------------------------------------------------------------------------------------------

GLF updates personally built live boot Linux OS variants on an approximately monthly schedule, incrementing the version date and version number with each new build.  GLF uses the Debian-supported "live build" system to produce the OS build ISO images.  This system was on a basic level constructs an OS image by downloading and installing the latest available binary packages from the Debian repositories into a chroot environment such that a fully functional installed live bootable DVD or USB image can be produced, according to a list of specifications, and/or by overriding or extending default installations with additional files proveded in a base configuration fileset.

GLF maintains archived *.tar.gz filesets as the complete configuration used to build each OS build variant and version.  These are intended to make each build replicable except to the extent to which repository package updates take precedence. In general, a given build variant is updated by extracting all the files from a prior version of that variant to a file folder, then changing the folder name and its contents to reflect the new version number, along with any other intended changes to the configuration files therein.

If no other changes are made to the configuration than the following basic example, which updates only the version number, then the new build will be equivalent to the prior build except that all available updates for repository packages will be performed, including any to the underlying Linux OS itself.  This should keep the live boot OS distribution as stable yet secure as practical over time.  

Note that the following procedures assumne that all the pertinent folders and files exist on a Linux EXT4 filesystem partition.  Trying to do this on a Windows NTFS or other partition type may not work due to different treatment of permissions and symlinks.

For this document, the SLICK distribution version 730 will be used as an example.


The basic SLICK 730 AMD64 configuration fileset tree as unpacked (folders only):

   slick730_amd64
   ├── auto
   ├── config
   │   ├── apt
   │   ├── archives
   │   ├── bootloaders
   │   ├── debian-installer
   │   ├── hooks
   │   │   ├── live
   │   │   └── normal
   │   ├── includes
   │   ├── includes.binary
   │   │   ├── boot
   │   │   │   └── grub
   │   │   └── isolinux
   │   ├── includes.bootstrap
   │   ├── includes.chroot
   │   │   ├── etc
   │   │   │   ├── chromium
   │   │   │   ├── live
   │   │   │   │   └── config.conf.d
   │   │   │   └── skel
   │   │   │       ├── Desktop
   │   │   │       ├── Documents
   │   │   │       ├── Downloads
   │   │   │       ├── Public
   │   │   │       └── Templates
   │   │   ├── run
   │   │   │   └── resolvconf
   │   │   └── usr
   │   │       ├── local
   │   │       │   └── bin
   │   │       └── share
   │   │           ├── applications
   │   │           ├── cups
   │   │           │   └── model
   │   │           ├── fonts
   │   │           │   └── truetype
   │   │           │       ├── barcode
   │   │           │       ├── pcl
   │   │           │       ├── trs80
   │   │           │       └── XPTChords
   │   │           └── ventoy
   │   │               ├── boot
   │   │               ├── tool
   │   │               └── ventoy
   │   ├── includes.installer
   │   ├── includes.source
   │   ├── package-lists
   │   ├── packages
   │   ├── packages.binary
   │   ├── packages.chroot
   │   ├── preseed
   │   └── rootfs
   └── local
       └── bin

If the builder intends to make no changes to the next build other than the basic general update, then the only files which need editing attention are the following:

   The main folder name, which embeds the version number, needs to be renamed (ex. slick730_amd64).

   The two files "binary" and "common" under the "config" subfolder which embed the version number.
      Edit these files to change that number where it occurs (search for "730", replace with "731").

   Under "config/includes.binary/isolinux", edit "splash.png" to embed the version number and date,
      then replace it and in addition, copy it to "config/includes.binary/boot/grub".  
      Use "Pinta" application to edit the PNG file.  An extra file omitting the version number and date
      is provided as a template (ex. "64_unlabeled_splash.png").
    
   Certain other variants might also include an additional file containing the version number under
      "config/includes.chroot/var/GLFPE_install", the file "aboutglfpe.ini" embeds the version number and
      date.
      
   Edit the "STATUS" text file under the main folder to reflect the version date and any configuration
   changes.   

Assuming there are no other intended changes to application lists or overriding data, recompress the main file folder to a *.tar.gz archive.  For most GLF OS variants, the "Engrampa" file archiver utility will be all that is necessary to compress the configuration fileset (ex. "slick731_amd64.tar.gz").

However, certain more complicated special variants include internal symlinks which fail to properly archive using the GUI "Engrampa" utility (ex. GPERS, GWINE).  For those, a command line compression must be performed to avoid corrupting the symlink pointers. and rendering the configuration unusable the next time.  The command line model can be used for ANY of the variants, but for simpler cases (such as SLICK) the GUI method is usually OK and more convenient.  

For those cases where the command line is needed, the following example may be used as a template (execute from the overriding folder which CONTAINS the target "slick731_amd64" folder):

   tar -zcvf slick731_amd64.tar.gz slick731_amd64/   
   
Note the slash at the end of the second argument -- it is necessary to identify the name of a folder rather than a file.

After compressing the archive of a configuration fileset, be sure to verify the archive is successful by using the 'Engrampa" utility to open and examine the aarchive.  If everything worked, one should be able to open and examine the top level file folder within the archive and several folders or files under it.  If the decompression fails, you must try the archive compression again, or the configuration will not be suitable for the next update process.

DON'T throw away any of the configuration sets until you KNOW you won't need then again (if a build is buggy you may need to revert something to an earlier version).

