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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Build casacore 3.5.0 #9

Open
wants to merge 8 commits into
base: master
Choose a base branch
from
Open

Build casacore 3.5.0 #9

wants to merge 8 commits into from

Conversation

ludwigschwardt
Copy link
Collaborator

@ludwigschwardt ludwigschwardt commented Jun 12, 2024

  • Build the released casacore 3.5.0.
  • I had to include the Add missing include in test聽casacore#1350 fix as a temporary patch. I also removed an old Python 2 patch. We should be patch-free after the next release 馃檪
  • Build Python bindings by default now, as I keep on forgetting to specify it. Who doesn't need it anyway? The upside is that we can now have Python-enabled bottles for the first time 馃帀
  • Upgraded the Homebrew actions so that tests pass and we have bottles (ventura-intel and sonoma-arm).
  • Updated casacore-data measures, for what it's worth.
  • Advertise my nifty historical graft to make older commits visible during logs and blames.

Use latest stable version from GitHub.

The new Dysco storage manager needs GSL, and Python 2 support is now
disabled by default.
We need a new stable version every two months...
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.
We almost always want Python bindings. Rather disable Python explicitly
with `--without-python` in case you don't.
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
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
Copy link
Collaborator Author

The tests pass again and we have bottles :-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant