[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Adding use-package to core
From: |
xenodasein |
Subject: |
Re: Adding use-package to core |
Date: |
Sun, 13 Nov 2022 17:11:57 +0100 (CET) |
From: Eli Zaretskii
Subject: Re: Adding use-package to core
Date: Sun, 13 Nov 2022 09:31:11 +0200
> I don't share Stefan's fears. If the only issue with moving
> use-package to core is that someone must step forward to take the
> responsibility for maintaining it, I think we can move it into core
> without fear. I see no reason for making a dedicated maintainer for
> use-package a prerequisite for importing it, given what John says
> about its stability. It's a non-issue.
Why don't you? This package has been very popular for a long time and
at least I haven't seen anyone complain about it not being in core.
Whatever gets included seem to freeze in time and becomes very hard to
make non-breaking changes, and their writers probably get frustrated
from that more easily and stop developing it. There's ever more lines of
code and more packages, I don't think this direction is sustainable and
I hope you will reconsider this approach of adding everything to core
at some point.
- Re: Adding use-package to core, Payas Relekar, 2022/11/13
- Re: Adding use-package to core,
xenodasein <=
- Re: Adding use-package to core, Stefan Kangas, 2022/11/13
- Message not available
- Re: Adding use-package to core, xenodasein, 2022/11/13
- Re: Adding use-package to core, Stefan Kangas, 2022/11/13
- Re: Adding use-package to core, Eli Zaretskii, 2022/11/13
- Re: Adding use-package to core, xenodasein, 2022/11/13
- Re: Adding use-package to core, Eli Zaretskii, 2022/11/13