Date: Thu, 26 Dec 2013 06:54:51 -0500 From: Jerry <jerry@seibercom.net> To: FreeBSD Ports <freebsd-ports@freebsd.org> Subject: Re: Updating CUPS Message-ID: <20131226065451.745a0c55@scorpio> In-Reply-To: <fe29d3d0-4035-4a66-860e-35a6f795ce32@email.android.com> References: <20131224154419.1b87ef83@scorpio> <fe29d3d0-4035-4a66-860e-35a6f795ce32@email.android.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 25 Dec 2013 09:14:55 +0100, Matthias Andree stated:
> Jerry <jerry@seibercom.net> schrieb:
> >The ports latest version of CUPS is 1.5.4; however version 1.7.0 has
> >been out since 10/24/13. Is there any possibility that the latest
> >version will make it into the ports system soon?
> >
> Careful with what you are asking for, have you checked the upstream
> change logs? 1.6 already broke some aspects of compatibility
> massively w.r.t. distributed printing or differing CUPS versions in
> your LAN.
Well, almost any updated software has the potential to break something,
CUPS being no exception. However, those cases are not the norm and the
fact that in a few edge cases problems have been discovered is not a
sound reason for unilaterally failing to include the new version in the
posts system. There have been numerous cases where a new version of a
port was introduced into the system. In many of those cases workarounds
were introduced to allow the user to continue with the older version or
update to the newer one. I fail to see why that would not be acceptable
in this instance. In any case, how do you propose to find problems with
a new product if it is not tested in a real environment? In a worse
case scenario, a new port, perhaps "cups-devel" could be created.
--
Jerry
{Please don't CC me. I am on the list.}
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20131226065451.745a0c55>