[Letux-kernel] New LetuxOS kernel trees for Replicant

[H. Nikolaus Schaller]

> Am 29.06.2019 um 22:02 schrieb Andreas Kemnade <andreas at kemnade.info>:
> 
> On Sat, 29 Jun 2019 21:53:54 +0200
> "H. Nikolaus Schaller" <hns at goldelico.com> wrote:
> 
>> Hi,
>> I have updated the replicant variants of our source tree
>> 
>> 4.10.5 -> 4.14.129			http://git.goldelico.com/?p=letux-kernel.git;a=shortlog;h=refs/heads/letux-4.14.129-replicant
>> work/josua/android-4.17 -> 4.19.56	http://git.goldelico.com/?p=letux-kernel.git;a=shortlog;h=refs/heads/letux-4.19.56-replicant
>> 
>> There were only minor merge conflicts, mostly in Kconfig and Makefile.
>> Only the two patches for the lowmemorykiller did not apply on 4.19.56, so they are missing:
>> 
>> http://git.goldelico.com/?p=letux-kernel.git;a=commit;h=fbc6ce18694bf8c255525327674598e5ed3b9ced
>> http://git.goldelico.com/?p=letux-kernel.git;a=commit;h=6c77d5cea4464c40dcfa382e096252c3cafae1b7
>> 
>> I have not been able to really test these kernels but we should continue fixing them because those are now long-term kernels.
>> 
>> So we should update the manifest files to point to these branches.
>> 
>> What I am not exactly sure about is if we should include the full version number in the branch name, i.e. "letux-4.19.56-replicant" which
>> means we will create newer and newer branches with different names over the time and have to make the manifest track that. This more or less treats git branches like git tags (and is not more resource hungry).
>> 
>> Or if we should have a single branch "letux-4.19-replicant" where we merge in future branches.
> 
> This with CONFIG_LOCALVERSION_AUTO=y,
> then we know which kernel we are using.

Well, the uImage can always queried by "file" and the running system by "uname".

I think this CONFIG adds the -gxxxxxxxx things which gives a different version even if
you have local unpublished patches...

So I thing that will break the LetuxOS kernel build system.

Note that we also have separate subfolders on

	http://download.goldelico.com/letux-kernel/?C=M;O=D

and I'd like to keep that for convenience in several aspects. For example having full subversion numbers makes this a real archive. But I don't want to have -gxxxxxxxx version names and separate every single build attempt.

Without having a version suffix in the branch name at all, newer versions will overwrite the older ones.
And makesd allows to specify exactly which version to install.

Well, there is a different approach. Automatically making a second branch name alias.

We already do that for (currently) letux-4.19.56 which has the alias name "master".

So we could define "letux-4.19-replicant" always be the same HEAD as e.g. "letux-4.19.58-replicant".
This should be easily added to my build server scripts and essentially is the combination of the contradicting approaches :)

I have manually done the push now, so you can see them at

	http://git.goldelico.com/?p=letux-kernel.git;a=heads

being the same. And everyone can chose in the manifest to include the latest or a specific version.

BR,
Nikolaus