NETWAYS / NETWAYS/support-collector
Check for "genuine packages"
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 0
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
We could use a more thorough check of which packages were installed:
- Were the packages provided by the actual vendor (e.g. Icinga) or were they custom built by the user or someone else?
- Are these release packages or devel snapshots?
I know, that's not possible to determine on every platform but where we can, we should collect the information.
Background: At least once we took some time hunting down a bug only to realize that the user had built custom packages using wrong libraries. The tool worked more or less but had some issues that were directly linked to using the wrong libraries. Since this is all but common it took us quite a while to find out.
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
No files, tests, or entry points are named. Locate where support-collector gathers installed-package information and review the platform-specific metadata available; done means recording vendor provenance and distinguishing release packages from development snapshots wherever the platform permits.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- operating-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 32/100