Opened 3 weeks ago

Closed 2 weeks ago

#15097 closed enhancement (wontfix)

scons-4.1.0.post1

Reported by: Bruce Dubbs Owned by: blfs-book
Priority: normal Milestone: 10.2
Component: BOOK Version: git
Severity: normal Keywords:
Cc:

Description

I'm not sure what to make of this package. The name suggests that it is a development version, but at https://sourceforge.net/projects/scons/files/scons/ it says this is the latest version.

On the other hand, https://github.com/SCons/scons says that version 4.1.0 is the latest package.

I suggest we wait for at least a couple of weeks to see if there is anything more.

Another option is to just change the currency script to determine the latest version from the data at github.

Change History (2)

comment:1 by ken@…, 3 weeks ago

I'm used to sourceforge equating 'latest' with 'development', but I've never seen a 'post' version of a package before. <sarcasm>But it's python, where they seem to like to invent wheels</sarcasm>

The version is definitely distinct from 4.1.0, but the CHANGES.txt and RELEASE.txt files, although dated for 28th May, do not seem to mention anything after 4.1.0.

OTOH, https://scons.org/pages/download.html says 4.1.0post1 is a production release, but the ChangeLog link on that page give a github 404. Although post1 at sourceforge is dated 28th May, the last changes at github are currently 14 and 17 days ago (CHANGES.txt, RELEASE.txt) - reading CHANGES.txt there it looks as if this is on the way to 4.2.0. From memory, biber has "next" versions (next number, contents can change) at sourceforge. So I think this is a step on the way to 4.2.0.

To me this unconventional naming is just another pythonista weirdness. Unless one of our python users corrects me, I'd say go with the latest version from github.

But I agree that leaving it to see if there is anything more is probably as good an approach as any. AFAICS, only serf in the book can use it.

comment:2 by Bruce Dubbs, 2 weeks ago

Resolution: wontfix
Status: newclosed

Changed currency to use github where what we have now is current. Won't fix.

Note: See TracTickets for help on using tickets.