<div dir="ltr"><div dir="ltr">On Mon, 18 Nov 2019 at 21:09, Khem Raj <<a href="mailto:raj.khem@gmail.com" target="_blank">raj.khem@gmail.com</a>> wrote:<br></div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On Mon, Nov 18, 2019 at 6:33 AM Alexander Kanavin<br>
<<a href="mailto:alex.kanavin@gmail.com" target="_blank">alex.kanavin@gmail.com</a>> wrote:<br>
><br>
> The homepage: <a href="https://www.kernel.org/doc/man-pages/download.html" rel="noreferrer" target="_blank">https://www.kernel.org/doc/man-pages/download.html</a><br>
> specifies that the latest tarballs are published one level up<br>
> from where we currently take them.<br>
><br>
<br>
archive is a better location for what it's worth. Since long after a<br>
release, the tarball may disappear from<br>
level up but chances of it being in archive are higher. So Let's not<br>
change this URI, unless there is another<br>
reason that I missed.<br></blockquote><div><br></div><div>I have to disagree actually! The reasons are:</div><div>1. Taking man-pages from archive means we are always shipping an out of date version, particularly if a tarball is archived months or years later than it was released.<br></div><div>2. Specifically here, the main folder has all man-page releases going back 1.5 years, which is longer than yocto release's support window. Meanwhile, the archive is missing several latest releases.<br></div><div>3. Even if a yocto release ships a version of man-pages that is then archived and removed from main folder, it is trivial and safe to backport an update from master. man-pages tarballs contain pre-built documentation and don't threaten release stability.</div><div><br></div><div>If this becomes a real problem, we can also write to Michael Kerrisk and ask that he doesn't move tarballs around.<br></div><div><br></div><div>Alex<br></div></div></div>