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

Yeet static builds + vendoring #63

Merged
merged 4 commits into from
Dec 28, 2024
Merged

Yeet static builds + vendoring #63

merged 4 commits into from
Dec 28, 2024

Conversation

samcday
Copy link
Owner

@samcday samcday commented Dec 27, 2024

No description provided.

@samcday samcday force-pushed the yeet-static-plus-vendoring branch 2 times, most recently from 943db5b to 2ce7d68 Compare December 28, 2024 15:51
@samcday
Copy link
Owner Author

samcday commented Dec 28, 2024

Also yeeting Packit builds until #23 is completed, as those RPM builds were relying on the vendored libphosh-rs

@samcday samcday force-pushed the yeet-static-plus-vendoring branch 3 times, most recently from d0519fa to 257ba25 Compare December 28, 2024 16:18
In the early development of phrog, this was much more useful. Now, it's
a liability. The subtree merges are inexplicably brutal, even though the
vendorered trees here don't diverge *that* much. It's just not worth the
effort, especially since the upstream codebases are much more active
than this project is or ever will be.

Ultimately, there was never going to be any significant number of folks
running a build of phrog with phosh statically linked, besides local
development. The latter case will be more friction-y for sure, but oh
well.
@samcday samcday force-pushed the yeet-static-plus-vendoring branch from 257ba25 to 8840a43 Compare December 28, 2024 16:31
@samcday samcday merged commit b89edb4 into main Dec 28, 2024
5 checks passed
@samcday samcday deleted the yeet-static-plus-vendoring branch January 2, 2025 11:29
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.

1 participant