pelican: update to 4.11.0. #55822
Open
pelican: update to 4.11.0. #55822
+87
−20
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jason1987d
changed the title
jason1987d
force-pushed
the
pelican
branch
3 times, most recently
from
93d86d3 to
69c40a6
Compare
jason1987d
force-pushed
the
pelican
branch
2 times, most recently
from
30d9852 to
53366fa
Compare
jason1987d
changed the title
|
Do people install Pelican directly from an xbps package? I use it but keep it updated using pip. With this method (and venvs) it can be managed by the user and doesn't need to be installed system-wide. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Testing the changes
New package
Local build testing
Noticed pelican was way out of date. Was attempting to build a website with hugo, which had too many issues with its themes, so coming back to this tool.