Le Mon, Jun 29, 2026 at 09:53:01PM +0800, Chris Billington a écrit :
> Stuart Henderson wrote:
> > On 2026/06/29 17:05, Chris Billington wrote:
> > : * Chromium -> ${SYSCONFDIR}/chromium/unveil.main
> > : * Firefox -> ${SYSCONFDIR}/firefox/unveil.main
> > : * Iridium -> ${SYSCONFDIR}/iridium/unveil.main
> > : * Ungoogled-chromium -> ${SYSCONFDIR}/ungoogled-chromium/unveil.main
> >
> > this is a total pain because now the user will have to manage the
> > unveil files themselves and merge in any changes after updates to the
> > browser ports. the pkg-readme would at least need to inform the user
> > about this, but it would be better if these could be included in the
> > relevant files directly in the browser ports (though 'r' for all of
> > /usr/local/bin might be a bit much)...
> >
>
> When browser updates are installed, there is a message about checking
> unveil.content/unveil.main "which was modified" though I found this actually
> refers to the package copy, not the local version, so any extra lines in the
> local copy are preserved. Then use 'sysmerge -p' to bring in any updates to
> the package version.
>
> Maybe I can add a note about 'sysmerge -p' to this README? This could also
> be added to keepassxc README as it's the same situation.
i dunno what is "the best way to document that" but people should
definitely get used to run sysmerge -p as much as sysmerge for base.
especially for those cases.
