Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.kernel > #64326 > unrolled thread

Kernel 5.2 in experimental branch.

Started byMmobilea <nobilea100@gmail.com>
First post2019-06-22 17:50 +0200
Last post2019-06-25 18:20 +0200
Articles 2 — 2 participants

Back to article view | Back to linux.debian.kernel


Contents

  Kernel 5.2 in experimental branch. Mmobilea <nobilea100@gmail.com> - 2019-06-22 17:50 +0200
    Kernel 5.2 in experimental branch. "Enrico Weigelt, metux IT consult" <lkml@metux.net> - 2019-06-25 18:20 +0200

#64326 — Kernel 5.2 in experimental branch.

FromMmobilea <nobilea100@gmail.com>
Date2019-06-22 17:50 +0200
SubjectKernel 5.2 in experimental branch.
Message-ID<ybQr7-3oM-3@gated-at.bofh.it>

[Multipart message — attachments visible in raw view] — view raw

Hello,
I have an question. I recentlly saw a kernel version in fedora rawhide 5.2. Why it isn’t on debian experimental branch
Sorry for errors. I’m new on debian.
Greatings and nice day

Wysłane z aplikacji Poczta dla Windows 10

[toc] | [next] | [standalone]


#64339

From"Enrico Weigelt, metux IT consult" <lkml@metux.net>
Date2019-06-25 18:20 +0200
Message-ID<ycWkO-2rw-5@gated-at.bofh.it>
In reply to#64326
On 22.06.19 17:31, Mmobilea wrote:
> Hello,
> 
> I have an question. I recentlly saw a kernel version in fedora rawhide
> 5.2. Why it isn’t on debian experimental branch

linux-5.2 upstream isn't final yet (still rc6).

And the debian kernel build system is really complicated. I have no idea
why it is so complicated, but I really believe, we should clean it up.

The package tries to build several completely different trees at once.
It makes several copies of the orig tree and applies different patch
queues (which seem to be maintained pretty manually), for different
flavours. And the magic for constructing the actual .config's is also
pretty complex and hard to understand and maintain.

IMHO, the best approach would be having separate source packages for
the individual flavours, and maintain everything directly in git
(yes: no text patches at all).

With a few minor patches (*1), we can directly use the existing upstream
`make deb-pkg` machinery via usual debuild+friends toolchains - all it
then takes is adding the proper .config file and fire it up to builldd.
Really, it can be *sooo* simple.

*1) https://github.com/metux/linux/commits/wip/debian-master


--mtx

-- 
Enrico Weigelt, metux IT consult
Free software and Linux embedded engineering
info@metux.net -- +49-151-27565287

[toc] | [prev] | [standalone]


Back to top | Article view | linux.debian.kernel


csiph-web