Re: Fedora Modularity: What's the Problem?

2019-11-04 Thread Randy Barlow
On Mon, 2019-11-04 at 03:18 +0100, Kevin Kofler wrote: > > *Requirement*: Users must be able to discover what alternative > > software > > versions are available with tools that are shipped with the OS by > > default. > > Ideally, these should be the same tools that they are already > >

Re: Fedora Modularity: What's the Problem?

2019-11-03 Thread Kevin Kofler
Stephen Gallagher wrote: > One of the recurring themes in the ongoing Modularity threads has been > that we've made references to the problems we're trying to solve, but we > haven't done a good job of gathering those requirements and use-cases into > a single place. To resolve this, I've written

Re: Fedora Modularity: What's the Problem?

2019-10-31 Thread Zbigniew Jędrzejewski-Szmek
On Mon, Oct 28, 2019 at 03:56:11PM -0400, Stephen John Smoogen wrote: > I think the issue is that neither of you are defining what expected > lifespans of stability or what stability is. After that you can > disagree whether it is important or not to what you want to do... but > until then you are

Re: Fedora Modularity: What's the Problem?

2019-10-28 Thread Fabio Valentini
On Mon, Oct 28, 2019 at 8:21 PM Stephen Gallagher wrote: > > On Mon, Oct 28, 2019 at 2:16 PM Zbigniew Jędrzejewski-Szmek > wrote: > > > > Hi, > > > > Thank you for this very useful summary. > > > > One general problem with the thinking behind this is that it applies much > > more > > to CentOS

Re: Fedora Modularity: What's the Problem?

2019-10-28 Thread Randy Barlow
On Mon, 2019-10-28 at 15:35 -0400, Neal Gompa wrote: > If we could operate on spec files and SRPMs, then the Gentoo solution > gets to be an interesting option. Yeah that's what I'm suggesting - to study Gentoo's solution and to make similar changes to our tooling to achieve a similar solution.

Re: Fedora Modularity: What's the Problem?

2019-10-28 Thread Stephen Gallagher
On Mon, Oct 28, 2019 at 4:11 PM Zbigniew Jędrzejewski-Szmek wrote: > > On Mon, Oct 28, 2019 at 03:11:13PM -0400, Stephen John Smoogen wrote: > > On Mon, 28 Oct 2019 at 14:38, Neal Gompa wrote: > > > > > > On Mon, Oct 28, 2019 at 2:16 PM Zbigniew Jędrzejewski-Szmek > > > wrote: > > > > > > > > >

Re: Fedora Modularity: What's the Problem?

2019-10-28 Thread Zbigniew Jędrzejewski-Szmek
On Mon, Oct 28, 2019 at 03:11:13PM -0400, Stephen John Smoogen wrote: > On Mon, 28 Oct 2019 at 14:38, Neal Gompa wrote: > > > > On Mon, Oct 28, 2019 at 2:16 PM Zbigniew Jędrzejewski-Szmek > > wrote: > > > > > > > > > > > > *Requirement*: It must be possible for the packager to specify the >

Re: Fedora Modularity: What's the Problem?

2019-10-28 Thread Stephen John Smoogen
On Mon, 28 Oct 2019 at 15:21, Stephen Gallagher wrote: > > On Mon, Oct 28, 2019 at 2:16 PM Zbigniew Jędrzejewski-Szmek > wrote: > > > > Hi, > > > > Thank you for this very useful summary. > > > > One general problem with the thinking behind this is that it applies much > > more > > to CentOS or

Re: Fedora Modularity: What's the Problem?

2019-10-28 Thread Randy Barlow
On Mon, 2019-10-28 at 15:33 -0400, Randy Barlow wrote: > Gentoo's solution to "too fast, too slow" addresses every requirement > in this post, except for this one: > > On Mon, 2019-10-28 at 10:08 -0400, Stephen Gallagher wrote: > > Requirement: Packagers must be able to encode whether their

Re: Fedora Modularity: What's the Problem?

2019-10-28 Thread Neal Gompa
On Mon, Oct 28, 2019 at 3:33 PM Randy Barlow wrote: > > Gentoo's solution to "too fast, too slow" addresses every requirement > in this post, except for this one: > > On Mon, 2019-10-28 at 10:08 -0400, Stephen Gallagher wrote: > > Requirement: Packagers must be able to encode whether their output

Re: Fedora Modularity: What's the Problem?

2019-10-28 Thread Randy Barlow
Gentoo's solution to "too fast, too slow" addresses every requirement in this post, except for this one: On Mon, 2019-10-28 at 10:08 -0400, Stephen Gallagher wrote: > Requirement: Packagers must be able to encode whether their output > artifacts are intended for use by other projects or if they

Re: Fedora Modularity: What's the Problem?

2019-10-28 Thread Stephen Gallagher
On Mon, Oct 28, 2019 at 2:16 PM Zbigniew Jędrzejewski-Szmek wrote: > > Hi, > > Thank you for this very useful summary. > > One general problem with the thinking behind this is that it applies much more > to CentOS or RHEL than it does to Fedora. In particular: > > users want a solid, stable,

Re: Fedora Modularity: What's the Problem?

2019-10-28 Thread Stephen John Smoogen
On Mon, 28 Oct 2019 at 14:38, Neal Gompa wrote: > > On Mon, Oct 28, 2019 at 2:16 PM Zbigniew Jędrzejewski-Szmek > wrote: > > > > > > *Requirement*: It must be possible for the packager to specify the order > > > in > > > which packages must be built (and to indicate which ones can be built

Re: Fedora Modularity: What's the Problem?

2019-10-28 Thread Neal Gompa
On Mon, Oct 28, 2019 at 2:16 PM Zbigniew Jędrzejewski-Szmek wrote: > > Hi, > > Thank you for this very useful summary. > > One general problem with the thinking behind this is that it applies much more > to CentOS or RHEL than it does to Fedora. In particular: > > users want a solid, stable,

Re: Fedora Modularity: What's the Problem?

2019-10-28 Thread Zbigniew Jędrzejewski-Szmek
Hi, Thank you for this very useful summary. One general problem with the thinking behind this is that it applies much more to CentOS or RHEL than it does to Fedora. In particular: > users want a solid, stable, reliable, *unchanging* system. In that case, really, Fedora is not the answer. No

Fedora Modularity: What's the Problem?

2019-10-28 Thread Stephen Gallagher
One of the recurring themes in the ongoing Modularity threads has been that we've made references to the problems we're trying to solve, but we haven't done a good job of gathering those requirements and use-cases into a single place. To resolve this, I've written a (fairly long) blog post

Fedora Modularity: What's the Problem?

2019-10-28 Thread Stephen Gallagher
One of the recurring themes in the ongoing Modularity threads has been that we've made references to the problems we're trying to solve, but we haven't done a good job of gathering those requirements and use-cases into a single place. To resolve this, I've written a (fairly long) blog post