Re: Proposing rpm-ostree jigdo ♲📦 discussion for the next meeting
On Mon, Dec 4, 2017, at 03:22 PM, Colin Walters wrote:
- Do OIRPMs appear in the Everything repo? (I hope so but it's
not required)
Actually I forgot to mention the sub-thread from
https://github.com/projectatomic/rpm-ostree/issues/1081#issuecomment-3419...
and my reply:
https://github.com/projectatomic/rpm-ostree/issues/1081#issuecomment-3420...
Basically to really preserve the experience we need to keep older RPMs
around in a "reliable" way - at least the last release, and my preference would
be 2-3 or
more. This might be something where we e.g. pass
"fedora-atomic-host-27.8"
as the "$releasever" variable to
metalink=https://mirrors.fedoraproject.org/metalink?repo=fedora-$releasev...
and mirrormanager DTRT? Maybe it'd be more reliable though to pass a distinct
variable though.
Also, from this comment:
https://github.com/projectatomic/rpm-ostree/issues/1081#issuecomment-3485...
Given how very prominent the repo IDs will be, I'd like to consider renaming
`[fedora]` to `[fedora-major-release]` or something, and then
`[updates]` to `[fedora-updates]`? Or possibly just `[fedora]`?
(Using [] around the name to clarify these are rpm-md repo IDs for things
that appear in /etc/yum.repos.d)
If we don't do this we can probably hack around it with some metadata
to tell rpm-ostree to present [updates] as [fedora-updates]` or so).