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

For høge krav i configure.ac? #5

Open
erikbs opened this issue Jan 18, 2025 · 3 comments
Open

For høge krav i configure.ac? #5

erikbs opened this issue Jan 18, 2025 · 3 comments

Comments

@erikbs
Copy link

erikbs commented Jan 18, 2025

apertium-nno og apertium-nob krev lttoolbox 3.7.8 og cg3 1.4.8, endå den siste utgjevne utgåva av lttoolbox er 3.7.6 og av cg3 1.4.6. Veit ikkje med apertium-nob, men apertium-nno byggjer dersom eg set ned kravet i configure.ac til desse (testa kje å køyra). Er det nokon grunn til å setja kravet so høgt eller kann det setjast ned til lttoolbox 3.7.6 og cg3 1.4.6?

@TinoDidriksen
Copy link
Member

Development requires nightly versions of tools, and those versions are high enough.

@erikbs
Copy link
Author

erikbs commented Jan 19, 2025

Is master perhaps not intended for non-development use, then? The reason why I ask is that I want to see if it would be possible to add Apertium language data as packages in the MacPorts system (Apertium is already there, but it does not include any languages). The releases of nno and nob are fairly new and could be used as is, but eng has not had a release in 4-5 years and quite a few languages have no releases at all (e.g. Greek, Bulgarian and Welsh). Even though there are no releases for Welsh, there are two for the language pair English+Welsh, so I would guess that the fact that a language has no releases does not necessarily mean that the data for that language is not ready for production use? Do the different language data repos have different policies?

It makes sense that development requires nightly versions, but are they required for just using the data? If not, could the requirements be lowered and a note about using the nightly tool versions for development be added instead?

@TinoDidriksen
Copy link
Member

The master and main branches are all development branches. Releases are explicitly tagged. If there is no such tag, then it's either ancient (as in, from before the move to GitHub) or no release has been made.

The MacPorts packages are all rather out of date, since we just use my nightly binary builds (https://apertium.projectjj.com/osx/install-nightly.sh + https://apertium.projectjj.com/osx/install-nightly-data.sh).

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

No branches or pull requests

2 participants