mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Christian Melki <christian.melki@t2data.com>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH] rules/module-init-tools: Enable zlib compression support.
Date: Mon, 11 Oct 2021 09:44:50 +0200	[thread overview]
Message-ID: <a1250115-08a6-4e11-cf99-1095d4c41031@t2data.com> (raw)
In-Reply-To: <20211011064809.GB28441@pengutronix.de>



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
ptxdist@pengutronix.de
To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-request@pengutronix.de


      reply	other threads:[~2021-10-11  7:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-09 12:01 Christian Melki
2021-09-29 11:26 ` Michael Olbrich
2021-10-08 20:28   ` Christian Melki
2021-10-11  6:48     ` Michael Olbrich
2021-10-11  7:44       ` Christian Melki [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=a1250115-08a6-4e11-cf99-1095d4c41031@t2data.com \
    --to=christian.melki@t2data.com \
    --cc=ptxdist@pengutronix.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox