On 13 July 2010 21:53, Philipp Überbacher email@example.com wrote:
Excerpts from Ray Rashif's message of 2010-07-13 15:38:04 +0200:
Currently extra/scons-1.3.0-1 is marked out-of-date, which is probably due to the fact that since last month, version 2 has become the stable branch upstream. From http://www.scons.org:
"14 June 2010 SCons production release 2.0.0.final.0 is now available from the download page at SourceForge. This is the production release for the 2.0 series. The 2.0 series drops support for all pre-2.4 versions of Python. See the ChangeLog for a complete list of changes in the release."
Version 1 is still supported, as evidenced by the development branch updates:
"26 June 2010 SCons release 1.3.0.d20100626 is now available from the download page at SourceForge. Fix the ability to append to default $*FLAGS values (which are implemented as CLVar instances) in a copied construction environment without affecting the original construction environment's value. See the ChangeLog for a complete list of changes in the release."
The following are the packages that makedepend on scons:
== extra == hydrogen ardour linuxdcpp
== community == ffmpeg2theora oregano btanks kleansweep pingus dangerdeep fceux mypaint glob2
We can either update it to version 2 or move version 1 to a scons1 package. If there are no objections and build issues, I'll go ahead with the former, as it doesn't appear to be that popular to warrant both major branches in the repos.
I do expect issues. There were scons issues with ardour in the past. ardour3 moved to waf and that's where devlopment is going on. They likely aren't interested in fixing scons issues when they arise. I guess testing will scons2 will show which way to go.
scons 2.x is now in [testing] - it will replace scons 1.x in [extra].
I had tested all affected packages and they built fine, but for anyone else with corner cases, please file a bug upstream.
-- GPG/PGP ID: B42DDCAD