jean-michel wroteFirst, after a talk on arch channel, and a test I made myself with a simple pkgbuild to reproduce our case, pacman does not touch things it doesn't know about.
Yes, but in your case (at 0.2.3.0-1 version) pacman know about /etc/66/service because it create by the makefile. When you run makepkg, you will have a resulting empty directory pkg/etc/66/service. So pacman know about this directory.
Second, I was curious if I can reproduce this issue with an upgrade from this last 66 0.2.3.2-1 version to a new one I made myself without any change inside the pkgbuild. The fact is, the empty /etc/66/service is not removed anymore.
Yes, you got the point of my change. Installing empty directories by pacman was clearly a bad behavior (proof on this update). So from the 0.2.3.2-1 version , this trouble will not be seen anymore. Also, other "distro" will be happy with this change too.
So in my own conclusion, the change eric introduce on the 66 source code between the version 0.2.3.0-1 and 0.2.3.2-1 is the only reason of this issue and should not happen again with the next 66 upgrade.
correct :)
fungalnet wrotebut if it is not empty it is not removed, right?
if it was the case the /var/lib/66 would have been erased