Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: "Thomas Bonnefille" <thomas.bonnefille@bootlin.com>
Cc: buildroot@buildroot.org, "Miquèl Raynal" <miquel.raynal@bootlin.com>
Subject: Re: [Buildroot] [PATCH v2] package/libsha1: Fix gcc14 compilation in libsha1
Date: Mon, 16 Dec 2024 23:10:11 +0100	[thread overview]
Message-ID: <20241216231011.39e908c6@windsurf> (raw)
In-Reply-To: <D6DFB2M8HLES.RY7H0ZIZNUBO@bootlin.com>

On Mon, 16 Dec 2024 21:56:04 +0100
"Thomas Bonnefille" <thomas.bonnefille@bootlin.com> wrote:

> > But more importantly: https://github.com/pseiderer/libsha1/ isn't
> > "upstream". Upstream for this package is
> > https://github.com/dottedmag/libsha1. So we're interested in seeing
> > the change having been submitted or accepted by the real upstream, not
> > just a commit in some "random" Github repository (even though Peter
> > Seiderer is a well known Buildroot contributor!)  
> 
> Ok so a link to the pull-request is probably better here according to BR
> documentation.
> (https://github.com/dottedmag/libsha1/pull/1)

Yes, that's the reference we want indeed.

> However, in this case the PR may not be merged soon given the date of
> the last commit applied to the upstream package.

Gah, indeed. I tried quickly to find another "upstream", but there
doesn't seem to be an obvious upstream alternative. This package is
used by xwayland and xserver_xorg-server as a minimal alternative to a
full-blown crypto library like OpenSSL or libgcrypt.

I think for now, your change with Upstream:
https://github.com/dottedmag/libsha1/pull/1 is going to be good enough.
We can always separately decide if we want to drop this package
entirely.

Thanks a lot!

Thomas
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2024-12-16 22:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-16 17:48 [Buildroot] [PATCH v2] package/libsha1: Fix gcc14 compilation in libsha1 Thomas Bonnefille
2024-12-16 20:36 ` Thomas Petazzoni via buildroot
2024-12-16 20:56   ` Thomas Bonnefille via buildroot
2024-12-16 22:10     ` Thomas Petazzoni [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=20241216231011.39e908c6@windsurf \
    --to=thomas.petazzoni@bootlin.com \
    --cc=buildroot@buildroot.org \
    --cc=miquel.raynal@bootlin.com \
    --cc=thomas.bonnefille@bootlin.com \
    /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