On Thu, Nov 15, 2018 at 5:44 AM Pierre-Yves Chibon <pingou(a)pingoured.fr> wrote:
On Wed, Nov 14, 2018 at 11:36:44AM -0500, Owen Taylor wrote:
> Thanks for starting this discussion, Matthew!
>
> A few notes:
>
> * My personal long-term dream is that all Fedora users are running
> Silverblue, we do great automated QA testing, and upgrading from one
> Fedora to the next is a non-event, and opt-out rather than opt-in, and
> long term support would not be needed. We aren't there yet. :-)
> * If we have a long-term support branch, the stuff that's in the
> default install / the stuff that would be in a Silverblue image -
> should be rebased very sparingly. I think we'd have to define this set
> - it's bigger than the current "critical path".
> * As we move higher up the stack, it's more reasonable for
> maintainers to take an approach of maintaining a single version across
> active Fedora branches - and we have various mechanism to make that
> easier: packages.cfg, module stream expansion, Flatpaks.
packages.cfg?
I'm not sure I know what this refers to, would you have any pointers?
It's a new unknown feature of rpkg (and thus fedpkg) to let you
configure `fedpkg build` to build packages for multiple koji targets
at once from a single branch. If you choose to have a single "master"
branch instead of a branch for every distro release, you can use that
file to specify what distribution releases you should build for by
default with `fedpkg build`.
--
真実はいつも一つ!/ Always, there's only one truth!