Make EPICS_HOST_ARCH available to hook scripts

Open
  • Is something wrong?
#80 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
38/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
ci-cd

Research direction

Start by reading prepare() and the detect_epics_host_arch() and add_dependency() functions mentioned in the issue. Check how *_HOOK scripts receive their environment, then determine where EPICS_HOST_ARCH can be made available. Done means a hook can use that variable to select configure/CONFIG_SITE.Common.$(EPICS_HOST_ARCH).

Written by the indexing model from the issue text.

Description

enhancement

I would find it helpful to have $EPICS_HOST_ARCH available in *_HOOK scripts. eg. to write configure/CONFIG_SITE.Common.$(EPICS_HOST_ARCH).

I am not quite sure of the best way/place to add this. Maybe as simple as moving detect_epics_host_arch() before add_dependency() in prepare()?

Dominant language
Python
Stars
8
Forks
21
Avg merge
13h 50m
Merged PRs (30d)
3

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from epics-base/ci-scripts

All issues in epics-base/ci-scripts

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.