On Thursday, 22 October 2020 2:16:16 AM AEDT Sean Whitton wrote:
> I think that we can all agree with everything you've written about the
> reasons why packaging components separately is better.
> The problem is
> that in this case the choice seems to be between not having recent
On Wednesday, 21 October 2020 8:56:53 PM AEDT Felix Lechner wrote:
> How is the second one inferior, please? I think it includes a crucial
> missing feature (co-installable versions).
To reduce maintainers burden, you want maintainers to look after not one but
multiple versions of libraries.
On Wednesday, 21 October 2020 12:52:40 PM AEDT Felix Lechner wrote:
> > We favour technical elegance often in expense of maintainers' comfort.
> Is our approach really either one of those? I think our response to
> the vendoring explosion is at odds with the trends in many languages.
On Tue 20 Oct 2020 at 06:52pm -07, Felix Lechner wrote:
> I think our response to the vendoring explosion is at odds with the
> trends in many languages.
> It's time to retool. At the two ends of the solution spectrum, I see
> 1. Fully vendored source packages; or
> 2. A
Hello security team,
The TC are being asked about src:kubernetes, and it would be good to
hear from you about whether and how security support is a relevant
consideration in determining whether the level of vendoring in that
package is acceptable. Could you take a look at #971515 and perhaps
On Wed, Oct 21, 2020 at 12:50 AM Dmitry Smirnov wrote:
> Yes, at first there will
> be a significant effort but then it will become easier.
I know you put a lot of effort in (as did Michael Stapelberg, with
whom I spent some time before he left), but I don't think our current
On Wed 21 Oct 2020 at 11:21am +11, Dmitry Smirnov wrote:
> On Wednesday, 21 October 2020 6:16:03 AM AEDT Sean Whitton wrote:
>> I think that my message  is what makes you think that the package
>> would not have got through NEW?
> It was not your message but my own experience
Mail list logo