All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Dario Binacchi <dario.binacchi@amarulasolutions.com>
Cc: Samuel Martin <s.martin49@gmail.com>,
	linux-amarula@amarulasolutions.com, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/armadillo: bump to version 10.1.0
Date: Fri, 30 Aug 2024 18:47:14 +0200	[thread overview]
Message-ID: <20240830184714.539c1fb0@windsurf> (raw)
In-Reply-To: <CABGWkvrSzFdKqrZ1MWm76kEtd=GigJA5_FwYq3smQJW734S6xw@mail.gmail.com>

Hello Dario,

On Tue, 27 Aug 2024 08:20:30 +0200
Dario Binacchi <dario.binacchi@amarulasolutions.com> wrote:

> This is the response from Conrad Sand, one of the two maintainers of
> the project:
> 
> ---------------------------------------------------------------------------------------------------
> Hi Dario,
> 
> Armadillo 9.900 is very old, horribly outdated and no longer supported.

Right, but this is not a reason for the tarball to no longer be
available, as it breaks build systems horribly.

> I recommend upgrading to the latest version, which is currently 14.0.2.
> https://sourceforge.net/projects/arma/files/armadillo-14.0.2.tar.xz
> 
> If you really want ancient versions of Armadillo, they can be
> temporarily found here:
> 
> https://sourceforge.net/projects/arma/files/retired/

Did you try using those?

> ---------------------------------------------------------------------------------------------------
> 
> So, should I restore the  9.900 version?

Yes, for master, I would prefer to keep the 9.900 version.

> Or at this point, would it be acceptable to bump to 10.10?
> Or should I restore 9.900 and then bump to 10.10?
> Or should I restore 9.900 and then bump to 14.2?

This last choice is the right one: restore 9.900 in master, and bump to
14.0.2 in next, of course if you're interested by the package.
Otherwise, we could also decide to drop the package entirely. Samuel
Martin is associated to its in the DEVELOPERS file, but Samuel has
stopped contributing to Buildroot years ago, and nobody else got
interested by that package. Therefore dropping it would be a totally
acceptable alternative.

Best regards,

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-08-30 16:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-24 15:15 [Buildroot] [PATCH 1/1] package/armadillo: bump to version 10.1.0 Dario Binacchi
2024-08-26 16:57 ` Thomas Petazzoni via buildroot
2024-08-27  6:11   ` Dario Binacchi
2024-08-27  6:20   ` Dario Binacchi
2024-08-30 16:47     ` Thomas Petazzoni via buildroot [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=20240830184714.539c1fb0@windsurf \
    --to=buildroot@buildroot.org \
    --cc=dario.binacchi@amarulasolutions.com \
    --cc=linux-amarula@amarulasolutions.com \
    --cc=s.martin49@gmail.com \
    --cc=thomas.petazzoni@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.