Feature request: Adds XDG folder structure creation when adding users
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 974
- Forks
- 296
- Avg merge
- 6d 14h
- Merged PRs (30d)
- 9
Description
Created originally in Butane by @quentin9696: https://github.com/coreos/butane/issues/537
Podman strongly push to use quadlets to run containers via systemd units (https://docs.podman.io/en/latest/markdown/podman-systemd.unit.5.html)
When I want to create my units and my .container file, I need to always create my XDG structure first. For every user, I need to create the XDG structure, like
- path: /home/logging/.config
user:
name: logging
group:
name: logging
- path: /home/logging/.config/containers
user:
name: logging
group:
name: logging
- path: /home/logging/.config/containers/systemd
user:
name: logging
group:
name: logging
- path: /home/logging/.config/systemd
user:
name: logging
group:
name: logging
- path: /home/logging/.config/systemd/user
user:
name: logging
group:
name: logging
- path: /home/logging/.local
user:
name: logging
group:
name: logging
- path: /home/logging/.local/state
user:
name: logging
group:
name: logging
I'm thinking to a way to automate the creation, but it seam that skel cannot be used (https://discussion.fedoraproject.org/t/etc-skel-not-used-for-core-user-in-fedora-coreos/36973/4?replies_to_post_number=4)
Do you have any plan to integrate the XDG folder structure when adding a new user in butane?
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
The issue names no Ignition file, test, or entry point. Start by reviewing how user creation and directory creation are represented, then clarify the supported XDG behavior and required tests; done should mean users can receive the requested directories without manual entries.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- operating-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100