Date: Mon, 15 Jan 2018 16:51:54 +0100 From: Kurt Jaeger <lists@opsec.eu> To: Michael Gmelin <freebsd@grem.de> Cc: freebsd-ports@freebsd.org Subject: Re: Newer FreeBSD version for package breaks binary updates Message-ID: <20180115155154.GW2827@home.opsec.eu> In-Reply-To: <CDA28861-A8EF-4696-87A6-8DA21A603817@grem.de> References: <20180115155518.78223869@bsd64.grem.de> <398ccb7e-6d47-9566-eed6-230953ba903e@FreeBSD.org> <CDA28861-A8EF-4696-87A6-8DA21A603817@grem.de>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi! > I understand that message, but besides that this was hardly a > problem in the past (especially for minor version differences), it > also forces people to update at the same time as FreeBSD package > builders, which has consequences. For current, yes. That's the bleading edge stuff anyway... > Is adding this dependency really what we want, will package builder > updates scheduled in a predictable way, so system update cycles of > users can be aligned, etc.? Otherwise this just adds another way > to cut users from updating packages/forces them back to building > packages themselves. The question is: who from the non-developer user-base really uses current ? And those from the developer-base: Who has their own package-builder ? -- pi@opsec.eu +49 171 3101372 2 years to go !
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20180115155154.GW2827>