jebrhansen+SBo at gmail.com
Sun Apr 19 23:25:36 UTC 2020
On Sun, Apr 19, 2020, 5:02 PM Rich Shepard <rshepard at appl-ecosys.com> wrote:
> Well, the U. of Oregon again failed your ISP's SPF test so my message to
> your linux.com address was again rejected. Sheesh.
> ---------- Forwarded message ----------
> Date: Sun, 19 Apr 2020 15:59:19 -0700 (PDT)
> From: Rich Shepard <rshepard at appl-ecosys.com>
> To: Christoph Willing <chris.willing at linux.com>
> Subject: Re: Numpy3 (fwd)
> On Mon, 20 Apr 2020, Christoph Willing wrote:
> > Yes, the email arrived OK.
> Interesting. Wonder why the original message didn't make it there.
> > About numpy3, the reason for not upgrading is to maintain version sync
> > with numpy. Numpy is maintained by someone who prefers stability over
> > updates for no reason other than its availability. If you have a
> > particular reason for wanting/needing a newer version, I'm sure the
> > maintainer would be amenable to an update; then I could update numpy3.
> I keep python2 itself updated when a new version comes out because some
> applications, such as grass, still have not migrated to python3. My use is
> now all python3 so I don't bother upgrading python2 libraries.
> I've now no specific need for numpy3 and scipy3, but being 4 minor versions
> behind current seems a bit too much.
SBo has no official policy on how maintainers should upgrade their
packages. If there's no major bugs and no requirements by other software
for newer versions, some maintainers prefer to ride out there current
version until some bug is found or other software requires newer versions.
This is a similar stance taken by Pat in stable releases of Slackware. He
doesn't upgrade libraries in 14.2 just because newer versions are out.
This is why I said you may want to provide some reason on why the
maintainer should upgrade other than "there's a newer version".
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the SlackBuilds-users