-
-
Notifications
You must be signed in to change notification settings - Fork 6.1k
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
Fix build on Windows (restore tzinfo dependency) #1767
Conversation
For now you can add this to Gemfile
|
This project is essentially a To verify this, you can run the command # frozen_string_literal: true
source "https://rubygems.org"
gemspec |
It depends. I haven't found much information on possible recommendations, other than 9146. However, it's up to us to decide whether we want to allow users running theme locally on Windows to face the same problem or not. An alternative approach would be to add this information to the wiki. However, I don't think it is a good option to force people to spend time trying to find a solution. I urge you to think about which way to go: have a built-in fix to support Windows users, or add information to the wiki. Is there a downside for us to the first option? Thanks. |
I agree with @kungfux . I am a Windows user. After updating to v7.0.0, I will encounter the same error. Therefore I need to manually add |
Let me elaborate a bit more: the Gemfile of the main repository ( So how to make it easier for users to run Jekyll out of the box on Windows, I think we should restore As for the necessity of adding Windows timezone deps instructions to the Wiki, I think it's optional since they're already in the Jekyll docs and should be visible to new users when installing Jekyll, but I'm open to it if you insist.
I think this comment will help you understand the situation: jekyll/jekyll#5935 (comment) |
That's true for actions and maybe local development for some number of users, but not for everyone.
I'm the one who needs this added to both the starter and main repositories. I'm not going to estimate the number of Windows/Unix-like users and mention the availability of the GitHub workspace as a workaround. There is at least one user who has the problem of doing development on a Windows machine, and there is a chance that others will come along and file a ticket. I find it useful to build and see the result before committing changes to production. While I can modify and commit the Gemfile in my own blog instance, I have to keep the modified Gemfile locally while working with the main repository. IMO, if the extra dependency does not cause problems in the build process on Unix-like systems, and the only reason to remove it was to have a cleaner gem spec, then it is worse to have it by default. I trust your experience and believe you will make the right decision. I just wanted to share my experience regarding this change. Thanks for your time and for sharing useful links that I missed. P.S. Interesting point in that Jekyll blog post:
I have tried and created a new theme with Jekyll 4.3.3 and no tzinfo dependency has been added. However, I'm able to run |
Thanks for sharing this valuable experience, a better approach might be to customize a Docker development environment so that there are no cross-platform dependencies to worry about. In the past, the Gemfile in this repository has always had platform-specific dependencies because it was originally a regular Jekyll project (my personal website), and its dependencies were created with the
Maybe your machine has installed |
I see your point. I'll elaborate on that option and summarize results somewhere afterwards. Thanks. |
I'm considering using VS Code devcontainer to improve the development environment setup. |
That's what I've started to try following this guide as a starting point. However, it should be adapted to be suitable and fully automated. Preliminary, it looks interesting but I'm a bit concerned about the required additional resources. I will see how it goes :) |
I've been experimenting for a few hours with reference to the VS Codoe docs and will submit a PR later to improve it with you. |
Type of change
Description
Build is failing on Windows.
Additional context
Root cause: f87fdd0
Can we restore the dependency or is there a better solution?