8000 simplifying build process step2 in Azure Pipelines · Issue #287 · winpython/winpython · GitHub
[go: up one dir, main page]

Skip to content
simplifying build process step2 in Azure Pipelines #287
Open
@stonebig

Description

@stonebig

Build step should go in 3 isolated steps:

  • create_launcher should be moved at initial build step, along with scripts creation
  • define a predefined winpydir directory (no need to guess)
  • remove archis list
  • remove rootdir from everything (predefine a basedir and use CHANGELOGS_DIR instead)
  • simplify further changelogs following CHANGELOGS_DIR usage
  • pip install from requirements should be an independant mid-step,
  • create an installer should be an independant last step.

Nsis code should be more cleanly isolated along the way.
This should nicely fit the perspective of scipy wheels being in standard pypi this fall 2016

2016-04-08: I just discover that Almar Klein has given-up on "Pyzo" as a distribution:
pyzo/pyzo#379. "too much a burden"

To avoid that very same risk, work is going on this direction:

  • go down to 4 "fat" branches for WinPython 2016-03 (against 6 currently).
  • continue reducing NSIS dependance / code, (https://github.com/pfmoore/shimmy not moving but there may be a simpler solution)
  • simplify and improve WinPythonZero so that :
    . users can play a "receipe" or just "pip install" what they need over it (support mingwpy & friends)
    . the very same method can be used to build a "fat" branch in the cloud.
  • simplify WinPythonZero building experience, so that more WinPython users can become builders on-the-go, redo every WinPython creation and building step from scratch.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      0