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

move bootstrap to dev/make_dist.sh #1993

Merged
merged 1 commit into from
May 22, 2024

Conversation

edgarcosta
Copy link
Member

@edgarcosta edgarcosta commented May 22, 2024

In particular, moved
printf $flint_version > VERSION before ./bootstrap.sh
See: Homebrew/homebrew-core#166490 (comment)
and sagemath/sage#38048

@albinahlback
Copy link
Collaborator

Yeah, seems like I never updated the VERSION file for any patch I made. If it works, please merge when you feel it is ready.

@edgarcosta edgarcosta merged commit 45d2d28 into flintlib:main May 22, 2024
13 checks passed
@edgarcosta
Copy link
Member Author

I think I will need to make a couple more changes.

I triggered a release using this branch on my fork: https://github.com/edgarcosta/flint/releases/tag/v3.1.3-p1
and things work as expected.

flint-3.1.3-p1 # grep -rF "3.1.3-p1"
./configure:# Generated by GNU Autoconf 2.71 for FLINT 3.1.3-p1.
./configure:PACKAGE_VERSION='3.1.3-p1'
./configure:PACKAGE_STRING='FLINT 3.1.3-p1'
./configure:\`configure' configures FLINT 3.1.3-p1 to adapt to many kinds of systems.
./configure:     short | recursive ) echo "Configuration of FLINT 3.1.3-p1:";;
./configure:FLINT configure 3.1.3-p1
./configure:It was created by FLINT $as_me 3.1.3-p1, which was
./configure:FLINT_VERSION_FULL=3.1.3-p1
./configure:tail=3.1.3-p1
./configure:This file was extended by FLINT $as_me 3.1.3-p1, which was
./configure:FLINT config.status 3.1.3-p1

but the VERSION file still says 3.1.0 😭

@dimpase
Copy link
Contributor

dimpase commented Jun 25, 2024

Why don't you use ./configure to fill VERSION in ?

@edgarcosta
Copy link
Member Author

@dimpase where would ./configure get that information from?

@dimpase
Copy link
Contributor

dimpase commented Jun 25, 2024

how does one obtain the correct version in PACKAGE_VERSION ?

@edgarcosta
Copy link
Member Author

@dimpase
Copy link
Contributor

dimpase commented Jun 25, 2024

this does not look plausible - then PACKAGE_VERSION would still be 3.1.0, not what is shown above.

@dimpase
Copy link
Contributor

dimpase commented Jun 25, 2024

I am not sure what the problem is - for me, on the current main branch, version value in VERSION gets correctly written into flint.pc by ./configure.

By the way, it would be prudent to bump the minimal autoconf version in AC_PREREQ(2.62) to something sane, like 2.69.
Note that 2.62 is from 2008 and is really, really obsolete.

@edgarcosta
Copy link
Member Author

edgarcosta commented Jun 25, 2024

Releases are triggered via git tags, not necessarily by changing the file VERSION, and many times we forgot about that, e.g., https://github.com/flintlib/flint/blob/v3.1.3/VERSION

Now, we do printf $flint_version > VERSION in the github action, where $flint_version is the tag

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

3 participants