On Fri, Sep 01, 2017 at 09:25:22PM +1000, Nick Coghlan wrote:
> So the request is for there to be a way to indicate that a stream is
> available for explicit dependencies, but *shouldn't* be taken into
> account for implicit stream expansion yet. Then, once the low level
> stream is stable, *then*
On 31 August 2017 at 22:09, Matthew Miller wrote:
> On Thu, Aug 31, 2017 at 08:11:56PM +1000, Nick Coghlan wrote:
>> > I'd think the solution is simply to mark your module with "Service
>> > Level: alpha" (and then we'd want some tooling where SL-alpha and
>> > SL-beta modules only show up for tho
On Thu, Aug 31, 2017 at 08:11:56PM +1000, Nick Coghlan wrote:
> Yes, but our concern isn't with the Python module's dependencies on
> the Platform module, it's with *other* components that depend on the
> Python module: if stream expansion were to pick up all non-EOL
> branches as being "active", t
On 30 August 2017 at 21:56, Matthew Miller wrote:
> On Wed, Aug 30, 2017 at 07:43:21PM +1000, Nick Coghlan wrote:
>> As a concrete example, the upstream Python 3.7 alpha & beta cycle will
>> be running in parallel with the F28 development cycle. It would be
>> beneficial to be able to create the c
On Wed, Aug 30, 2017 at 07:43:21PM +1000, Nick Coghlan wrote:
> As a concrete example, the upstream Python 3.7 alpha & beta cycle will
> be running in parallel with the F28 development cycle. It would be
> beneficial to be able to create the corresponding module stream once
> the first alpha releas
On 9 August 2017 at 03:39, Ralph Bean wrote:
> ## Solution: "Input" Modulemd Syntax Changes
>
> We’re going to extend the modulemd syntax to allow specifying multiple
> dependencies in an "input" modulemd (the one that packagers modify). When
> submitted to the build system, the module-build-serv
On Tue, 2017-08-08 at 13:39 -0400, Ralph Bean wrote:
> ## Solution: "Input" Modulemd Syntax Changes
>
> We’re going to extend the modulemd syntax to allow specifying multiple
> dependencies in an "input" modulemd (the one that packagers modify). When
> submitted to the build system, the module-bu
On Tue, Aug 08, 2017 at 03:11:38PM -0400, Matthew Miller wrote:
> On Tue, Aug 08, 2017 at 09:04:40PM +0200, Petr Šabata wrote:
> > dependencies:
> > buildrequires: &deps
> > platform: [f28, f27, f26]
> > shared-userspace: [fancy, nonfancy]
> > requires: *deps
> >
> > Another
On Tue, Aug 08, 2017 at 09:04:40PM +0200, Petr Šabata wrote:
> dependencies:
> buildrequires: &deps
> platform: [f28, f27, f26]
> shared-userspace: [fancy, nonfancy]
> requires: *deps
>
> Another point that came up later -- instead of shared-userspace,
> imagine different str
On Tue, Aug 08, 2017 at 01:39:45PM -0400, Ralph Bean wrote:
> This is a writeup on a problem we’re facing with modularity, and some ideas on
> how to resolve it.
>
> # The "Problem"
>
> Imagine I have an **httpd module**. To simplify things, let’s say that this
> module has only one stream: **2.
This is a writeup on a problem we’re facing with modularity, and some ideas on
how to resolve it.
# The "Problem"
Imagine I have an **httpd module**. To simplify things, let’s say that this
module has only one stream: **2.4**. Today, in the modulemd for this module, I
declare build and runtime d
11 matches
Mail list logo
