Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Build casacore 3.5.0 on macOS #9

Merged
merged 9 commits into from
Jun 20, 2024
Merged

Build casacore 3.5.0 on macOS #9

merged 9 commits into from
Jun 20, 2024

Commits on Jun 11, 2024

  1. casacore 3.5.0

    Use latest stable version from GitHub.
    
    The new Dysco storage manager needs GSL, and Python 2 support is now
    disabled by default.
    ludwigschwardt committed Jun 11, 2024
    Configuration menu
    Copy the full SHA
    f8a6815 View commit details
    Browse the repository at this point in the history

Commits on Jun 12, 2024

  1. casacore-data 20240611

    We need a new stable version every two months...
    ludwigschwardt committed Jun 12, 2024
    Configuration menu
    Copy the full SHA
    e2bad2d View commit details
    Browse the repository at this point in the history
  2. casacore: Remove Python 2 patch and add #1350 fix

    Since we don't install the Python 2 bindings (called "python") anymore,
    it is safe to remove patches to that part of the code.
    
    Replace the old patch with a fix to the Dysco tests which was recently
    added to the development version in casacore/casacore#1350. This should
    be removed when we move to the next casacore release.
    ludwigschwardt committed Jun 12, 2024
    Configuration menu
    Copy the full SHA
    ac4c76b View commit details
    Browse the repository at this point in the history
  3. casacore: Build Python bindings by default

    We almost always want Python bindings. Rather disable Python explicitly
    with `--without-python` in case you don't.
    ludwigschwardt committed Jun 12, 2024
    Configuration menu
    Copy the full SHA
    ae8ed6d View commit details
    Browse the repository at this point in the history
  4. Add History section to README

    This is mostly to advertise the git replace mechanism used to link
    the older (ska-sa) commits before 2021 to the latest casacore project
    ones. This step (done per cloned local repository) allows `git log`,
    `git blame` and other commands to treat the two disparate histories
    as one.
    
    For the record, I followed these instructions:
    
    https://steemit.com/git/@sushrest/merging-2-repositories-to-preserve-history-using-grafting
    ludwigschwardt committed Jun 12, 2024
    Configuration menu
    Copy the full SHA
    4dfa6a9 View commit details
    Browse the repository at this point in the history
  5. Configuration menu
    Copy the full SHA
    bd803c5 View commit details
    Browse the repository at this point in the history
  6. Update to latest Homebrew tap actions

    I ran `brew tap-new --no-git test/tap` to get the latest GitHub
    workflows and copied the template over the existing ones. I might as
    well mention brew bundles in the README as well.
    ludwigschwardt committed Jun 12, 2024
    Configuration menu
    Copy the full SHA
    88ae5a5 View commit details
    Browse the repository at this point in the history
  7. Configuration menu
    Copy the full SHA
    88bdf17 View commit details
    Browse the repository at this point in the history

Commits on Jun 20, 2024

  1. Use master branch in GitHub Actions (for now)

    Ideally I would have liked to rename master branch to main instead, but
    this is in the midst of a PR with an open branch and it would therefore
    have been messy.
    ludwigschwardt committed Jun 20, 2024
    Configuration menu
    Copy the full SHA
    7ddba91 View commit details
    Browse the repository at this point in the history