<html><head></head><body><div>Hi Paul,</div><div><br></div><div>On Fri, 2024-01-12 at 20:12 +0100, Paul Gevers wrote:</div><blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex"><div>Hi Abou,<br></div><div><br></div><div>On 11-01-2024 20:40, Abou Al Montacir wrote:<br></div><blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex"><div>But this is the case of all lpk files where the binary package provide a <br></div><div>Manually compilable package while the source one provides a Compile As > Needed package file.<br></div></blockquote><div><br></div><div>Don't we want them to be the same? Why do we even ship the files twice?<br></div></blockquote><div>They are not the same for the following reasons:</div><div><br></div><div>When someone installs only binary packages (let's say an auto build setup) they don't want to recompile units, and they don't even install sources, so we tell lazbuild tool to not try to compile the units of this package. This is why the lcl-units-* binary packages provide lpk fills with <AutoUpdate Value="Manually"/>.</div><div><br></div><div>When a human installs full Lazarus on a desktop/laptop, he will want to install sources and may need to recompile Lazarus (unfortunately upstream does not support dynamically linked plugins and thus need to recompile lazarus when you install some new packages). This will fail with <AutoUpdate Value="Manually"/> and thus we change it to <AutoUpdate Value="AsNeeded"/>.</div><blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex"><div><br></div><blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex"><div>This was the case since many years now.<br></div></blockquote><div><br></div><div>Well, maybe I just didn't spot this issue before. But because of the <br></div><div>/usr-merged work of helmut, I'm much more aware of diversions so they'd <br></div><div>trigger me much more then they used to.</div></blockquote><div>Makes sense, but I'm not sure I understand why diverted files should be the same? Isn't diversion is used to enable a package to supersede another shipping a different version of the same file?</div><div><span><pre>-- <br></pre><pre>Cheers,
Abou Al Montacir
</pre></span></div></body></html>