From owner-freebsd-ports@FreeBSD.ORG Thu Dec 26 11:54:54 2013 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 5DB0CC5B for ; Thu, 26 Dec 2013 11:54:54 +0000 (UTC) Received: from mail-qe0-x22b.google.com (mail-qe0-x22b.google.com [IPv6:2607:f8b0:400d:c02::22b]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 114C7197A for ; Thu, 26 Dec 2013 11:54:53 +0000 (UTC) Received: by mail-qe0-f43.google.com with SMTP id jy17so7980689qeb.30 for ; Thu, 26 Dec 2013 03:54:52 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=seibercom.net; s=google; h=date:from:to:subject:message-id:in-reply-to:references:reply-to :mime-version:content-type:content-transfer-encoding; bh=FaukzRDZbw9XUOX5yVrin+IAH864vTCpIrlprBip6ew=; b=J724lIadslrUU3T8j2zHCZIVs19hWwMkBFmfl0JPpLAkxMtPe94L7ScsFRfPCAljbJ yl5ppNnf6SXptk5Z0EFZ9fXpmOyj9wxUKdXEA8HRtazicGrERxL6IAPoqd/AWtvgLek5 JvWpHDdsJUOotBTSSNNALYYnaOAX0AhrF+iqk= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:to:subject:message-id:in-reply-to :references:reply-to:mime-version:content-type :content-transfer-encoding; bh=FaukzRDZbw9XUOX5yVrin+IAH864vTCpIrlprBip6ew=; b=B4+bFSkGho2In4xBpQyCT+eHVj+TQX0bw2ssm2Sbn7SrbGjv2Jxyd56SxkVpy61M61 N4bbDvN8jFG/WPz7BCzGTf7hUsSmA+DFetYaMF6YG6FxSBo2ptqyBsnmxS+mPf7Pd49O EzbFCciVNaz3G/L8uzXne3o/7s7VG/cJNO2ucEtdUGeDM3blFOJDlQKgNaquL5wsx28+ 6yEN+jG10Zatx+5nDtixejss1LBgbj83eED+yBKAxdvyEIolZyf1R7J3NtdLS14zGk4l /OyHpaws0WhlN5GlpLTw8AmW6SggqfFZWgezk31OqGsU2bXRlqJ/up6nwkFK9OrTp6ZA MjjA== X-Gm-Message-State: ALoCoQnvGeg0jCSfXYSiI5uRcF8eNVyCwK2FiDx/HVVM1CJwQPO2DD1BUpaKIwCOMIYH5GHCFEdX X-Received: by 10.229.13.133 with SMTP id c5mr70105154qca.22.1388058892532; Thu, 26 Dec 2013 03:54:52 -0800 (PST) Received: from scorpio (cpe-076-182-104-150.nc.res.rr.com. [76.182.104.150]) by mx.google.com with ESMTPSA id ni10sm37517223qeb.23.2013.12.26.03.54.51 for (version=TLSv1.2 cipher=RC4-SHA bits=128/128); Thu, 26 Dec 2013 03:54:52 -0800 (PST) Date: Thu, 26 Dec 2013 06:54:51 -0500 From: Jerry To: FreeBSD Ports Subject: Re: Updating CUPS Message-ID: <20131226065451.745a0c55@scorpio> In-Reply-To: References: <20131224154419.1b87ef83@scorpio> X-Mailer: Claws Mail 3.9.3 (GTK+ 2.24.22; amd64-portbld-freebsd10.0) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list Reply-To: FreeBSD Ports List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Dec 2013 11:54:54 -0000 On Wed, 25 Dec 2013 09:14:55 +0100, Matthias Andree stated: > Jerry 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.}