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

Ubuntu-20 Support #145

Closed
wants to merge 53 commits into from
Closed

Ubuntu-20 Support #145

wants to merge 53 commits into from

Conversation

umagmrit
Copy link
Contributor

No description provided.

@umagmrit umagmrit marked this pull request as ready for review September 30, 2021 12:05
@umagmrit umagmrit marked this pull request as draft June 26, 2022 11:13
@umagmrit umagmrit force-pushed the release/ubuntu20 branch from d0af2f8 to 55e3577 Compare May 16, 2023 03:59
@adriangibanelbtactic
Copy link

freetype download url is 404.

Can you please fix the freetype download url as you did in Ubuntu 22.04 branch ( 0353bde#diff-210016897618936931351e7c3b13b5f97af7dd778ae2d666e43de2fe7960a0c6 ) ?

Thank you!

@umagmrit
Copy link
Contributor Author

Closing this PR as the changes have been integrated into #197

@umagmrit umagmrit closed this Nov 25, 2024
@adriangibanelbtactic
Copy link

Closing this PR as the changes have been integrated into #197

Does this mean that #197 associated branch which was originally meant to build Ubuntu 22.04 packages can be now used to build both Ubuntu 20.04 and Ubuntu 22.04 packages?

The freetype download url bug that I described above would be fixed.

In any case it's still not clear how to build packages for an specific ZCS Version+distro.
I mean, which branches need to be checked out for each case.

Yes, you pointed me in the right direction regarding Ubuntu 20.04 but there is not an official documented way of dealing with all of this.

First of all we need to know if the packages repo are:

  • Tied to a distro specific branch ( Ubuntu 20, Ubuntu 22 or RHEL9).
  • Tied to a ZCS version family specific branch ( 8.8.15, 9.0.0, 10.0.x, 10.1.x)
  • Tied to a combination of the above

And then it would be nice that those branches had proper names that explained what they were about.
E.g. you once had a release/ubuntu20 branch but you never had a release/ubuntu22 branch or release/rhel9 branch.

I'm asking for something similar to what it has already been done in zm-build repo for building an specific ZCS 10.0.8 version.

Thank you.

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.

2 participants