Accidentally I discovered this weirdness and don't know how it got to this, probably from the time I was building boot@ -66serv without a PKGBUILD
Fortunately they are configured the same, but why is version showing 2.2.1 and 66-env is picking up 2.2.0 ?
% lsd /etc/66/conf/boot@ sys/*/boot@ *
-rw-r--r-- 1 root root 4.6K Nov  1 16:48 '/etc/66/conf/boot@ sys/2.2.1/boot@ sys'
-rw-r--r-- 1 root root  532 Dec  2 00:31 '/etc/66/conf/boot@ sys/2.2.0/boot@ sys'
% sudo -E 66-env boot@ sys
This leads to editing the 2.2.0 file, not the 2.2.1
2.2.0 file has the fields with the comments removed, so it is smaller
% sudo 66-inservice -v3 -p3 boot@ sys   
Name                  : boot@ sys
Version               : 2.2.1
In tree               : boot
Status                : enabled, up
Type                  : module
Description           : Set of services to boot a machine
Source                : /usr/lib/66/service/boot@ sys
Live                  : /run/66/tree/0/boot/servicedirs/boot@ sys
Dependencies          : tty@ tty12 system-hostname mount-run populate-run mount-tmp populate-tmp
                        mount-proc mount-sys populate-sys mount-dev mount-pts mount-shm populate-dev
                        00 all-Mount system-hwclock modules-kernel system-random modules-system
                        system-sysctl udevd-log udevd udevadm system-fontnkey system-fsck
                        mount-fstab all-System mount-rw mount-swap local-loop local-sethostname
                        local-time local-authfiles local-tmpfiles local-dmesg all-Local all-Runtime
                        All tty-rc@ tty1 tty-rc@ tty2
External dependencies : None
Optional dependencies : None
Start script          : None
Stop script           : None
Environment source    : /etc/66/conf/boot@ sys/2.2.0
Environment file      : HOSTNAME=!bubba
                        TZ=Europe/Belgrade


Maybe this is why:
lrwxrwxrwx  1 root root   27 Sep 28 20:39 version -> '/etc/66/conf/boot@ sys/2.2.0'/
drwxr-xr-x 24 root root 4.0K Sep 28 20:39 2.2.0/
drwxr-xr-x  4 root root 4.0K Nov  1 16:48 ./
drwxr-xr-x 24 root root 4.0K Nov  1 16:48 2.2.1/
if you install a new version and enable it again without using any -c/m/C/i options the old version for the configuration file is kept.
You can see and handle it with 66-env 
# 66-env -V <service> # list all available version
# 66-env -c <version> service # set <version> as the default one to use
Ok, adjusted, but let's say boot@ -66serv 2.2.2 comes out, how does the user handle the upgrade, using the -c 2.2.2 option. I was under the impression things would work automatically.
Yes, -c option.

I need to find a smart way to simplify the thing for user.
I never checked because I was under the impression that when an upgrade comes it switches the version pointer to the new one. But as this directory structure is created by 66-enable (right?) it is not/can't be affected by pacman. So it would to be a script that checks and shifts? Then again, when the version shifts the module .conf is new, it is not the one edited with -env from last version... so it must be some way to read the values from the previous version and pass them into the new ... then runs enable -F again ... What a headache!
i will find a solution...

Powered by Obarun