Add an activation trigger feature #68

jhuntwork commented 2026年05月13日 17:01:55 +02:00

Mere needs a profile-activation trigger mechanism for derived files that depend on the fully realized profile, not on any single package store path. Example: GLib/GSettings packages install schema XML files under usr/share/glib-2.0/schemas, but applications such as Firefox expect a merged gschemas.compiled cache. Because Mere profiles are symlink trees assembled from immutable store objects, this cache should be generated after profile realization/activation against the merged profile root (e.g. run glib-compile-schemas $PROFILE_ROOT/usr/share/glib-2.0/schemas), not as a package-local post-install mutation. The same mechanism would likely apply to other desktop cache generators, and potentially other packages. This is generally analogous to post-install hooks in other systems.

Mere needs a profile-activation trigger mechanism for derived files that depend on the fully realized profile, not on any single package store path. Example: GLib/GSettings packages install schema XML files under usr/share/glib-2.0/schemas, but applications such as Firefox expect a merged gschemas.compiled cache. Because Mere profiles are symlink trees assembled from immutable store objects, this cache should be generated after profile realization/activation against the merged profile root (e.g. run glib-compile-schemas $PROFILE_ROOT/usr/share/glib-2.0/schemas), not as a package-local post-install mutation. The same mechanism would likely apply to other desktop cache generators, and potentially other packages. This is generally analogous to post-install hooks in other systems.