Gentoo Archives: gentoo-kernel

From: Tom Wijsman <TomWij@g.o>
To: gentoo-dev@l.g.o
Cc: gentoo-kernel@l.g.o
Subject: [gentoo-kernel] [PATCH] kernel-2.eclass: Add support for experimental genpatches.
Date: Tue, 03 Sep 2013 00:03:11
Message-Id: 20130903020253.4160868d@TOMWIJ-GENTOO
1 Hello everyone
4 Please only respond on the gentoo-dev ML.
6 Attached you will find a patch for kernel-2.eclass that adds support
7 for experimental genpatches; a response to the positive feedback on the
8 previous discussion [1], with subject "Proper distribution integration
9 of kernel *-sources, patches and configuration.". We also came up with
10 solutions for the negative feedback to get the best from both worlds.
12 [1]:
13 which starts in message ID <20130701164149.131490f8@TOMWIJ-GENTOO>
15 Its default functionality adds an USE flag which the users can use to
16 choose whether they want experimental patches or not; this behavior can
17 be further adjusted using three variables we provide, allowing the
18 ebuild writer to selectively decide how the patches are handled.
20 All possible combinations these variables as well as the USE flag can
21 be set in have been tested; so, in terms of functionality I think there
22 is nothing broken. mpagano and I have been using this during our recent
23 bumps as well; so, we are sure it doesn't break the default behavior.
25 The user can use both K_EXP_GENPATCHES_LIST and UNIPATCH_EXCLUDE to
26 respectively opt-in and opt-out control which experimental patches get
27 applied; this allows users to control them as they see fit.
29 Please note that we will check the patches to ensure they are guarded
30 by config checks; so, the sole reason the user has for doing the above
31 is to deal with possible collisions the user may have with user patches.
33 Please review the attached patch and let me know what you think...
35 Thank you in advance.
38 The rest of this mail are FAQ to attempt to answer common questions:
40 === How are the genpatches affected? ===
42 As for genpatches, patches in the 5000-5099 range will be stored in an
43 experimental tarball; so, they are distributed separately and are not
44 part of the base and extra tarballs. If the user or ebuild writer does
45 not explicitly choose for experimental, it will thus not be fetched.
47 === Are users that don't want experimental patches affected? ===
49 No, we will stay as stable and reliable as before; if users don't
50 explicitly opt in, they will not be affected by it on at least the
51 vanilla and gentoo sources. Other ebuild writers can see for themselves
52 if they want to defer from the defaults, but we encourage them not to.
54 Remember that with this change we try to deduplicate work; while doing
55 this, we do not force these patches on any user, there will be guards in
56 two places: The experimental USE flag and menuconfig. The new variables
57 in the eclass permit configuring which patches get applied as well.
59 === How will the users be aware of this? ===
61 We plan to write a news article to document this as well as create a
62 sub project page explaining the experimental patches and everything
63 that comes along (their status, how to enable, pick them, etc ...).
65 --
66 With kind regards,
68 Tom Wijsman (TomWij)
69 Gentoo Developer
71 E-mail address : TomWij@g.o
72 GPG Public Key : 6D34E57D
73 GPG Fingerprint : C165 AF18 AB4C 400B C3D2 ABF0 95B2 1FCD 6D34 E57D


File name MIME type
kernel-2.eclass.patch text/x-patch
signature.asc application/pgp-signature