1 |
On 14/1/19 10:27 pm, Rich Freeman wrote: |
2 |
> On Mon, Jan 14, 2019 at 7:47 AM Bill Kenworthy <billk@×××××××××.au> wrote: |
3 |
>> Hi, |
4 |
>> |
5 |
>> I am trying to find the ebuild and files for |
6 |
>> sys-kernel/gentoo-sources-4.18.20 but as its no longer in the tree I |
7 |
>> checked the attic but it looks like it is only cvs and no longer in use |
8 |
>> for git. |
9 |
>> |
10 |
>> I couldnt find gentoo sources in the server linked to from the cvs |
11 |
>> attic. Is there an equivalent to the attic for git, or a stanza to |
12 |
>> retrieve it? |
13 |
> If you have a git checkout, then chdir to the package directory, and |
14 |
> run "git whatchanged ." and search for the ebuild filename in the |
15 |
> output to find the commit where it was removed, then go one commit |
16 |
> further and check out that commit. |
17 |
> |
18 |
> If you want to do it on the web I'd: |
19 |
> |
20 |
> 1. go to https://gitweb.gentoo.org/repo/gentoo.git/ |
21 |
> 2. Click tree |
22 |
> 3. Navigate to the desired package directory |
23 |
> 4. Hit log |
24 |
> 5. Search for 4.18.20 if what you are looking for isn't in the last |
25 |
> page, or feel free to browse the history. |
26 |
> 6. Click on the most recent commit of interest. |
27 |
> 7. Find the ebuild in the commit, and click on its filename to get the |
28 |
> full contents of the ebuild. |
29 |
> 8. Click on the plain button next to the blob ID to get the raw |
30 |
> ebuild. For convenience it is: |
31 |
> https://gitweb.gentoo.org/repo/gentoo.git/plain/sys-kernel/gentoo-sources/gentoo-sources-4.18.20.ebuild?id=966dc9c8c004d79b02cb0250ecef65974164f295 |
32 |
> |
33 |
> If you're interested in running non-Gentoo-supported kernel series |
34 |
> though I'd suggest just using the upstream kernel repo directly. Then |
35 |
> you have access to upstream releases when they are released, even if |
36 |
> that series never gets a Gentoo ebuild. |
37 |
> |
38 |
> However, either way you ought to understand what you're doing. 4.18 |
39 |
> is not supported by upstream or Gentoo. The kernel will obviously |
40 |
> work the way it always did, but if there is a security update/etc you |
41 |
> won't get it. If you want to avoid significant kernel changes you |
42 |
> should try to settle on a longterm kernel, like 4.14 or 4.19, and then |
43 |
> just stick with it until a more recent longterm is appropriate. Those |
44 |
> get incremental stable updates for a long time. |
45 |
> |
46 |
> I think Gentoo's intent is to keep stable following a longterm branch, |
47 |
> but there were some issues with a recent longterm that probably has |
48 |
> derailed this a bit. I'm not on the kernel team so you're better off |
49 |
> going to them if there are questions. If you want to not have to |
50 |
> worry about maintenance then you should either follow upstream or |
51 |
> Gentoo, and setting out on your own should only be done to bisect |
52 |
> issues or when you know what you're doing... |
53 |
> |
54 |
Hi Rich, unfortunately 4.18.20 is the last one that supports the ipts |
55 |
patch set (surface pro4 touch screen) ... its flaky, bu the earlier ones |
56 |
are even worse so going to a LT kernel isnt really useful. I hope they |
57 |
can get a 4.19 or 4.20 patch set up soon, but apparently kernel changes |
58 |
have made it difficult. 4.19 without touch does work with only minor |
59 |
problems, but of course with no touch screen. |
60 |
|
61 |
BillK |