Eric, can you please stop to break 66?
66 got a lot of changes on this recent week (month). This is clearly annoying for you and also complicated to follow. I'm aware and understand this. Don't get me wrong, i do not apply changes for the pleasure or because it's fun (like other dev do, follows my regard). I try to give you the best and provide a robust software. After few month of use and reports, i saw what was good and what was not. The majorities of the changes that you apply implies a lot of works on the code part. So, you just see the top of the iceberg.
Fresh installation should give a smooth use of 66. The trouble comes when you need to update a version and this for two reasons.
The first one comes from skarnet softwares. When the skarnet softwares is updated (in particular skalibs and s6-rc), i need to follow and make changes according to his changes. Not every s6-rc update force to rebuild a compiled service database but it can. In this case you need to rebuild your tree.
The second reason comes directly from my part. Some important configuration files (transparent for you) are binaries (those files are in /var/lib/system/<tree>/servicedirs/.resolve). When i add/remove a field on this binary you need to enable again the service to rebuild those files.
The great majority of bad behaviour are now fixed. The new release (already in testing v0.2.1.2) will fix the last important change about logger and instanciated service. It miss us a another release (which is complete on my system v0.2.2.0) to change the 66-info behaviour. This software is horrible at use and horrible at the code part. This is now fixed and will be available soon.
From this two new release, you will be in peace for a couple of time :). I will make a great pause about 66 code (apart for bugs fix obviously),i will let 66 live by it own and i will wait for reports and advices.
Thanks for your patience, comprehension and to use 66.
Eric
66 got a lot of changes on this recent week (month). This is clearly annoying for you and also complicated to follow. I'm aware and understand this. Don't get me wrong, i do not apply changes for the pleasure or because it's fun (like other dev do, follows my regard). I try to give you the best and provide a robust software. After few month of use and reports, i saw what was good and what was not. The majorities of the changes that you apply implies a lot of works on the code part. So, you just see the top of the iceberg.
Fresh installation should give a smooth use of 66. The trouble comes when you need to update a version and this for two reasons.
The first one comes from skarnet softwares. When the skarnet softwares is updated (in particular skalibs and s6-rc), i need to follow and make changes according to his changes. Not every s6-rc update force to rebuild a compiled service database but it can. In this case you need to rebuild your tree.
The second reason comes directly from my part. Some important configuration files (transparent for you) are binaries (those files are in /var/lib/system/<tree>/servicedirs/.resolve). When i add/remove a field on this binary you need to enable again the service to rebuild those files.
The great majority of bad behaviour are now fixed. The new release (already in testing v0.2.1.2) will fix the last important change about logger and instanciated service. It miss us a another release (which is complete on my system v0.2.2.0) to change the 66-info behaviour. This software is horrible at use and horrible at the code part. This is now fixed and will be available soon.
From this two new release, you will be in peace for a couple of time :). I will make a great pause about 66 code (apart for bugs fix obviously),i will let 66 live by it own and i will wait for reports and advices.
Thanks for your patience, comprehension and to use 66.
Eric
