containers / containers/toolbox
Possibility to "rebase" a container
- Dominant language
- Go
- Stars
- 3.5k
- Forks
- 262
- Avg merge
- 3d 1h
- Merged PRs (30d)
- 1
Description
**Is your feature request related to a problem? Please describe.**
Currently, when updating say, from Fedora 38 to Fedora 39. You would usually stick with using your old container until at some point, one of your projects starts depending on a too new release of a package forcing you to create a new container. The creation bits are pretty straightforward; the annoying part is copying all you had installed and configured inside the old container and it would be pretty handy if toolbox could just do some parts of it for me, optionally.
**Describe the solution you'd like**
When running `toolbox create`, if the user has an old version of the distribution container, toolbox could ask to re-install the existing packages from the old one maybe?
**Describe alternatives you've considered**
Weird local shell scripts to make my life easier
**Additional context**
Nothing to add
Contributor guide
Research direction
Start with the `toolbox create` command and examine how it handles an existing older distribution container. Clarify which installed packages and configuration should be transferable, how the user would opt in, and what should happen when a package cannot be reinstalled. Done means an agreed, tested approach for optionally reusing relevant state when creating a newer container.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100