| 1 |
On Sat, Mar 7, 2020 at 9:57 AM Andreas Sturmlechner <asturm@g.o> |
| 2 |
wrote: |
| 3 |
|
| 4 |
> On Samstag, 7. März 2020 18:49:25 CET Ulrich Mueller wrote: |
| 5 |
> > Just the ebuild being outdated doesn't sound like a sufficient reason |
| 6 |
> > for removal of a package, at least not for those packages that install |
| 7 |
> > applications for the end user. |
| 8 |
> |
| 9 |
> They are python packages and as such they block cleanup of old python |
| 10 |
> versions. Someone has to actually put effort into each of them to keep |
| 11 |
> them |
| 12 |
> alive. |
| 13 |
> |
| 14 |
|
| 15 |
I think the idea is that this is all implicit in the notification, rather |
| 16 |
than being explicit, which muddles the messaging. I *suspect* that py3.6 |
| 17 |
will get dropped eventually as its no longer developed (but is security |
| 18 |
supported by upstream through 2021.) If we just came out and said "Hey we |
| 19 |
plan on dropping python-3.6 in X[0] months, here are a bunch of packages on |
| 20 |
py-3.6, we need to either drop them or update them" the conversation would |
| 21 |
be slightly different. |
| 22 |
|
| 23 |
I also suspect the conversation did not go this way because then instead of |
| 24 |
discussing who would maintain these packages, we would be discussing "why |
| 25 |
python-3.6 should not be dropped until the last possible day in 2021" which |
| 26 |
sounds reminiscent of python2 ;) |
| 27 |
|
| 28 |
I think however, that we can do both. Python-3.6 will get removed |
| 29 |
eventually; there are dozens of packages that need help and I don't think |
| 30 |
it is incumbent on the python team to do all of the work, hence this thread |
| 31 |
notifying folks that "hey if you use these packages they will need help to |
| 32 |
stay around." |
| 33 |
|
| 34 |
[0] We could all argue over some value of X; but on another thread please ;p |
| 35 |
|
| 36 |
|
| 37 |
> |
| 38 |
> > > But that's by no means all ebuilds like that, just a subset Python |
| 39 |
> > > team doesn't see much of a point maintaining. |
| 40 |
> > |
| 41 |
> > Why had they been added then, in the first place? |
| 42 |
> |
| 43 |
> Packages get added by someone, then that someone does not care about them |
| 44 |
> anymore and they fall behind. Is that really news? |
| 45 |
> |
| 46 |
> People who see a need for some of those can pick them up as maintainers |
| 47 |
> after |
| 48 |
> all. |
| 49 |
> |
| 50 |
> Regards, |
| 51 |
> Andreas |
Archives