getsops / getsops/sops

RPM package should install the sops binary to /usr/bin, not /usr/local/bin

Open
#1,216 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
23.1k
Forks
1.1k
Avg merge
1d 11h
Merged PRs (30d)
9

Description

I've noticed that the RPM files produced in releases unfortunately do not conform with Filesystem Hierarchy Standard 3.0 - https://refspecs.linuxfoundation.org/fhs.shtml

Specifically https://refspecs.linuxfoundation.org/FHS_3.0/fhs/ch04s09.html

/usr/local is clearly intended for software that you compile yourself, as in you run ./configure and then make install does the all target first to compile the software and install puts it in /usr/local. When you package things, you override the default prefix of /usr/local to /usr unless your project is needed for boot, like busybox.

Please fix this. Someone already ate your lunch when you weren't looking: https://copr-be.cloud.fedoraproject.org/results/harbottle/main/epel-8-x86_64/04392008-sops

Contributor guide

Open the contributing guide

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.

Research direction

No file, test, or release entry point is named in the issue. Start by locating the RPM packaging configuration used to produce release files, then verify that installing the RPM places the sops binary at /usr/bin/sops rather than /usr/local/bin/sops.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, linux
Domain
release
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.