Skip to content

fix(build): do not use tags for checkout#64

Merged
fathyb merged 1 commit into
fathyb:mainfrom
licy183:fix-for-patches
Feb 6, 2023
Merged

fix(build): do not use tags for checkout#64
fathyb merged 1 commit into
fathyb:mainfrom
licy183:fix-for-patches

Conversation

@licy183

@licy183 licy183 commented Feb 5, 2023

Copy link
Copy Markdown
Contributor

When chromium source is fetched with extra params --no-history, there will be no tag info in the local .git repository, and ./scripts/pacthes.sh apply will fail because git push --set-upstream origin fix-for-patches fails, so use the commit hash instead.

@fathyb fathyb merged commit 8dca13c into fathyb:main Feb 6, 2023
@fathyb

fathyb commented Feb 6, 2023

Copy link
Copy Markdown
Owner

Thank you!

@licy183 licy183 deleted the fix-for-patches branch February 6, 2023 11:35
jmagly added a commit to jmagly/carbonyl that referenced this pull request Apr 28, 2026
Both scripts already honoured CARBONYL_OZONE_TAG (added in 5e306d5),
but consumers needed a self-describing CLI surface — the env var was
easy to forget and easy to set in the wrong shell. Now:

  scripts/runtime-pull.sh --ozone=x11
  scripts/runtime-push.sh --ozone=x11

The CLI flag wins over the env var when both are set; passing the env
var still works (CI uses it). Default ozone is "headless" so existing
invocations are unchanged.

Also adds:
- -h/--help on both scripts that prints the in-file usage block
- Unknown-flag handling that exits 2 with a clear error
- Tag-shape rule comment in both scripts so they stay symmetric
- docs/runtime-modes.md: new "Fetching a runtime tarball" section that
  prefers the CLI flag over the env var for operator workflows

Closes fathyb#64
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