Incompatibility between doclicense and silence (Regression)

[ypid]

Incompatibility between doclicense and silence (Regression)

[ypid]

This seems to be caused by hyperxmp actually, maybe even the interaction between hyperref and hyperxmp. I am working on a warning similar to #69.

\RequirePackage{silence}
\documentclass[a4paper]{report}
\usepackage[hyperxmp=false,type={CC},modifier={by},version={4.0}]{doclicense}

\begin{document}
Thanks, you are welcome :)
\end{document}

[ypid]

I propose #83. But in your case, that results in a new warning from doclicense. I have the feeling that you don’t like warnings. Ideally, this would be fixed in hyperxmp or silence. They are both under the LaTeX Project Public License which actually defines how a new maintainer can take over maintenance. Please consider that.

[thbde]

Thank you very much for considering the issue. I really do not feel comfortable to put a burden here on doclicense as the issue seems to be caused by silence. The regression was the strong argument from my side as it could be frustrating for non-experts if they come back to a latex document and it hangs during compilation.

Regarding the change: I am not a Latex expert in detail. Maybe it could be possible to detect the issue on a "feature-level" instead of a package level? It may be unlikely to be soon, but if the silence package is fixed, then the check here might be wrong. I am honest, I will not remember this check in 10 years.

Other than that, it is a bit unfortunate that we do not get the metadata, but this is no showstopper.

I have the feeling that you don’t like warnings.

Well, point for you :) Warnings serve a purpose and therefore I try to get rid of them (without silencing them...).
Here, I could live with the approach proposed by #83. If I load the silence package, then I could also block this specific warning.

[ypid]

"feature-level" instead of a package level

Good idea but for that, I would need to debug the two packages to find the bug to do this feature or rather bug-level detection. And then I should rather fix the bug. But that is a bit out of scope for me.

So I merge #83 then. This workaround is in the workaround section and I will probably test if the workaround is still needed every other TeXLive release or so.

[thbde]

Ok, I understand. Fine for me. And again thank you very much for taking care of this issue.