Need to streamline requiring new version of packages (Trac #322)

[butlerpd]

Currently requiring a new version of, for example bumps, requires changes be made in five separate places: build_tools/* (mac builder, RPM builder and windows builder), setup.py and check_packages.py

Migrated from http://trac.sasview.org/ticket/322

{
    "status": "new",
    "changetime": "2019-02-03T04:20:59",
    "_ts": "2019-02-03 04:20:59.908754+00:00",
    "description": "Currently requiring a new version of, for example bumps, requires changes be made in five separate places: build_tools/* (mac builder, RPM builder and windows builder), setup.py and check_packages.py",
    "reporter": "butler",
    "cc": "",
    "resolution": "",
    "workpackage": "SasView Framework Enhancements",
    "time": "2015-02-14T14:01:13",
    "component": "SasView",
    "summary": "Need to streamline requiring new version of packages",
    "priority": "minor",
    "keywords": "",
    "milestone": "SasView 4.3.0",
    "owner": "",
    "type": "defect"
}

[butlerpd]

Trac update at 2015/03/10 15:18:54: butler commented:

want a configuration file that specifies all the version dependencies in one place to be used by the build systems.

[butlerpd]

Trac update at 2015/03/10 16:56:12:

• butler commented:

Not required for release and not likely to get done before release -- moving from 3.1 to release +1

• butler changed milestone from "SasView 3.1" to "SasView Next Release +1"

[butlerpd]

Trac update at 2015/08/14 20:11:01: butler changed milestone from "SasView Next Release +1" to "SasView 4.0.0"

[butlerpd]

Trac update at 2016/03/20 22:45:39: butler changed milestone from "SasView 4.0.0" to "SasView Next Release +1"

[butlerpd]

Trac update at 2019/02/03 04:20:59:

• butler commented:

Is this fixed by the yml files?

• butler changed milestone from "SasView Next Release +1" to "SasView 4.3.0"

[butlerpd]

@krzywon @rozyczko @wpotrzebowski @pkienzle - is this now fixed? I.e is there a single master list of dependencies? I think Jeff's checkpackages project now has that at least using the yml files. is that all we have now storing the versions? If so I can close this ticket. Otherwise will move it to 5.1

[krzywon]

In theory, the work I did on check packages could be a fix for this, but might require an update to the yaml files. In 5.x there are 10 different yaml files in the repo, each of which is used for something slightly different. I wasn't comfortable enough to add a new dependency I created for the check_packages because (1) I didn't know which of the yaml files I should edit and (2) I wasn't sure the proper versions for non-Windows systems.

A README in the /build_tools/ directory outlining what each file is used for might prove useful.