Skip to content

Do not require LIBCMARKDIR when GFM is unused#100

Open
Herrtian wants to merge 1 commit intoapache:masterfrom
Herrtian:fix-libcmarkdir-without-gfm
Open

Do not require LIBCMARKDIR when GFM is unused#100
Herrtian wants to merge 1 commit intoapache:masterfrom
Herrtian:fix-libcmarkdir-without-gfm

Conversation

@Herrtian
Copy link
Copy Markdown

@Herrtian Herrtian commented May 1, 2026

Fixes #83.

This defers the default cmark path handling until the Pelican subprocess environment is built. If the packaged cmark path exists, it is still passed through as before. If it does not, an existing LIBCMARKDIR in the environment is left alone, and non-GFM builds no longer fail while importing buildsite.py.

I also dropped the dummy LIBCMARKDIR from the postrun test so the no-GFM case is covered.

Checked with:

  • python3 -m py_compile bin/buildsite.py plugins/gfm.py
  • cd tests/postrun && unset LIBCMARKDIR && bash runtest.sh

@Herrtian Herrtian force-pushed the fix-libcmarkdir-without-gfm branch from c35f0e4 to 0f647af Compare May 1, 2026 15:20
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.

LIBCMARKDIR must be defined even if not needed

1 participant