Hello list. I'm working on the LibreWRT project [1] whish is based on OpenWRT [2]<div><br></div><div>The idea is to create an OpenWRT variant that would use only libre software. OpenWRT is composed of a bunch of scripts that download the kernel and the base system sources and compiles everything, producing a disk image. Different kernel versions are used for different target architectures.</div>
<div><br></div><div>As part of this work, we added a build option. When set, the kernel to download and compile should be Linux-Libre instead of the blobbed one. I made a POC which worked ok, and now I'm working on a clean patch to submit upstream to OpenWRT.</div>
<div><br></div><div>The patch should ideally just change the URL used to download the kernel, but this seems a bit hard, 'cause the directory structure & naming differs between <a href="http://kernel.org">kernel.org</a> and Libre Linux. Even worse, I see that some releases end in -libre, others in libre-1, libre-2, etc</div>
<div><br></div><div>So I'm writing to the list to know if there's a logic behind the naming scheme of Linux Libre, so that I can determine which is the folder and the name of the tarball that should be used for a given version. E.g. if kernel version is 2.6.32.14 how to know I should download 2.6.32.14-libre1/linux-2.6.32.14-libre1.tar.bz2 ?</div>
<div><br></div><div>I'm also curious about the reasons for not mirroring the <a href="http://kernel.org">kernel.org</a> directory & naming conventions, could someone illustrate me about this?</div><meta http-equiv="content-type" content="text/html; charset=utf-8"><div>
<br></div><div>Thanks in advance,</div><div>Antonio</div><div><br><div>[1] <a href="http://librewrt.org">http://librewrt.org</a></div>[2] <a href="http://openwrt.org/">http://openwrt.org/</a></div>