microsoft / microsoft/azure-linux-dev-tools
need way to include comps.xml into created local repo
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 18
- Forks
- 27
- Avg merge
- 4d 33m
- Merged PRs (30d)
- 24
Description
When using *only* a local repo, or only a remote repo that doesn't include any comps.xml, it's critical to include a proper comps.xml into the repo so mock is able to create the buildroot using the `@build` packages. This is simple to do, e.g. `createrepo -g /absolute/path/to/comps.xml /path/to/local/repo`, but the azldev tool does need to be updated to do either automatically or via config.
--
_Imported on behalf of @ddstreet_
Contributor guide
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 locating azldev's handling of local and remote repositories, then review how repository metadata is configured or generated. Reproduce the local-repository case with createrepo and the supplied comps.xml path. Done means a repository without comps.xml can provide the @build packages automatically or through documented configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- build-system, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100