Refactor usage of system commands to a module w/ autodiscovery or manually set $PREFIX?
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 24
- Forks
- 15
- Avg merge
- 13h 27m
- Merged PRs (30d)
- 3
Description
Currently, there are a few direct command invocations in solbuild, including calls to /bin/su.
To make it easier to update solbuild for the upcoming /usr merge task, consider how to consolidate known commands to a single module that adds (or discovers at startup?) the preferred location of commands.
The motive for possibly considering dynamic discovery of commands is that hard-coding commands is not really desirable if we want for solbuild to keep working outside of solus.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by inventorying solbuild's direct system-command invocations, including the /bin/su call. Compare a shared command module with startup discovery and manually configured $PREFIX, using the /usr merge context as the constraint. Done means command locations are consolidated and solbuild can keep working outside Solus without scattered hard-coded paths.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- build-system
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100