| 1 |
On Fri, 2021-07-23 at 00:47 +0900, Alice wrote: |
| 2 |
> On 7/23/21 12:43 AM, Michał Górny wrote: |
| 3 |
> > On Fri, 2021-07-23 at 00:24 +0900, Alice wrote: |
| 4 |
> > > On 7/23/21 12:02 AM, Michał Górny wrote: |
| 5 |
> > > > Why are you adding the USE flag for these kernels then? It's misleading |
| 6 |
> > > > at best. |
| 7 |
> > > |
| 8 |
> > > ah I just understand what are you asking. |
| 9 |
> > > that's right the USE flag on such kernel should be removed, |
| 10 |
> > > but I think is something that we can do in a next release of such kernel |
| 11 |
> > > and after removing this part from the eclass. |
| 12 |
> > |
| 13 |
> > Why not just unset the var in eclass? |
| 14 |
> > |
| 15 |
> |
| 16 |
> Because deblob works with python3 for kernel that are more recent than |
| 17 |
> 5.4 excluded. so I'm deprecating old kernel deblob that still use python |
| 18 |
> 2.7 and keep it for most recent one that can use python3. |
| 19 |
|
| 20 |
I'm saying that instead of printing ewarn for old kernels you should |
| 21 |
just disable the whole logic in eclass for old kernels. |
| 22 |
|
| 23 |
-- |
| 24 |
Best regards, |
| 25 |
Michał Górny |
Archives