On 10/11/21 8:48 AM, Michael Olbrich wrote:
On Fri, Oct 08, 2021 at 10:28:37PM +0200, Christian Melki wrote:
On 9/29/21 13:26, Michael Olbrich wrote:
On Thu, Sep 09, 2021 at 02:01:16PM +0200, Christian Melki wrote:
Let old and trusty module-init-tools handle zlib compressed kernel modules.
Any reason why you use this instead of libkmod? The module-init-tools are
no longer maintained, so I would actually prefer to move the package to
staging and remove it eventually. Unless there is a specific use-case for
them that does not work with libkmod?
Michael
Nope. No reason. Just compressed module support in case someone uses it.
I don't mind either way. But if it doesn't move to staging then you
might as well add compressed module support? I see no harm.
I'll move it to staging. I just wanted to make sure that there isn't a
use-case that requires it specifically.
While we're at it.. Why "staging" for obsoleted packages?
It started out as a place for badly maintained (in ptxdist) packages to
give people a chance to update and improve the rules before I remove them
completely.
I didn't want to create a different section for packages that just move
there to give people a change to update to something else.
How about obsolete for obsolescence and staging for the fashionable
kids? I think it makes it a whole lot clearer if you're unfamiliar with
whatever package.
The problem is, that there are always grey areas. So I want to keep all in
one section. When I move a package to staging, then I put a comment in the
menu file that should tell you why it's there.
Ack. Thanks for taking time to explain it.
Michael
_______________________________________________
ptxdist mailing list
[email protected]
To unsubscribe, send a mail with subject "unsubscribe" to
[email protected]
