From owner-freebsd-ports@FreeBSD.ORG Thu Dec 26 17:30:18 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 97AB2D06 for ; Thu, 26 Dec 2013 17:30:18 +0000 (UTC) Received: from mout.gmx.net (mout.gmx.net [212.227.15.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 30C8012C6 for ; Thu, 26 Dec 2013 17:30:17 +0000 (UTC) Received: from [10.253.225.108] ([46.115.93.225]) by mail.gmx.com (mrgmx001) with ESMTPSA (Nemesis) id 0Lk8CY-1VLX6D15hK-00c7Hh for ; Thu, 26 Dec 2013 18:30:16 +0100 User-Agent: K-9 Mail for Android In-Reply-To: <20131226065451.745a0c55@scorpio> References: <20131224154419.1b87ef83@scorpio> <20131226065451.745a0c55@scorpio> MIME-Version: 1.0 Subject: Re: Updating CUPS From: Matthias Andree Date: Thu, 26 Dec 2013 18:30:07 +0100 To: FreeBSD Ports Message-ID: <01418a96-df39-4a66-8ff6-004c67879290@email.android.com> X-Provags-ID: V03:K0:CEJnpPm+O/vtQEMmYJmnC8ATfwHR2CX7KKcmxdc5hrUoisQusnf W5qIJ18NmNSLFvLwds9iIOZ2C7dj8jVRFrPYHe9UtfXR/ZJF+tBkaYYVrUbO1kDSIA/pvrS 92uzN8XFQN9PoRnFi+K1Kd8vrG5CDWW5BnctPj422KY++KcJyG8dHXmbLMNXd74TyYAvl+l /V80przdR7BJfhjrgOGxw== Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.17 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Dec 2013 17:30:18 -0000 Jerry schrieb: >On Wed, 25 Dec 2013 09:14:55 +010= 0, Matthias Andree stated: > >> Jerry schrieb: >> >= The ports latest version of CUPS is 1=2E5=2E4; however version 1=2E7=2E0 ha= s >> >been out since 10/24/13=2E Is there any possibility that the latest >= > >version will make it into the ports system soon? >> > >> Careful with wh= at you are asking for, have you checked the upstream >> change logs? 1=2E6 = already broke some aspects of compatibility >> massively w=2Er=2Et=2E distr= ibuted printing or differing CUPS versions in >> your LAN=2E > >Well, almos= t any updated software has the potential to break something, >CUPS being no= exception=2E 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 un= ilaterally failing to include the new version in the >posts system=2E There= have been numerous cases where a new version of a >port was introduced int= o the system=2E In many of those cases workarounds >were introduced to allo= w the user to continue with the older version or >update to the newer one= =2E I fail to see why that would not be acceptable >in this instance=2E 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, pe= rhaps "cups-devel" could be created=2E > >-- >Jerry > >{Please don't CC me= =2E I am on the list=2E} >_______________________________________________ >= freebsd-ports@freebsd=2Eorg mailing list >http://lists=2Efreebsd=2Eorg/mail= man/listinfo/freebsd-ports >To unsubscribe, send any mail to >"freebsd-port= s-unsubscribe@freebsd=2Eorg" I meant deliberate changes in concepts, not j= ust happenstances=2E=2E=2E Check what Fedora and other Linux distros have b= een doing to work around those before you complain=2E And remember this i= s a volunteer project, you are not paying to get upgrades within the week= =2E=2E=2E From owner-freebsd-ports@FreeBSD.ORG Thu Dec 26 17:30:56 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 744CEDA2 for ; Thu, 26 Dec 2013 17:30:56 +0000 (UTC) Received: from mail-lb0-x230.google.com (mail-lb0-x230.google.com [IPv6:2a00:1450:4010:c04::230]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id ECDEB12D1 for ; Thu, 26 Dec 2013 17:30:55 +0000 (UTC) Received: by mail-lb0-f176.google.com with SMTP id l4so3758133lbv.21 for ; Thu, 26 Dec 2013 09:30:54 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:content-type; bh=PKpixecHvY9r7ctq2RLk9+RZ3YRiUDrqGhVYnka8QGk=; b=n2MfJblCRMLZc6L7T9BbWJolNPRCwA+8iYZAEtVN9N2JeeaLAWiE85pFv0e8UgCa5j iPPPHFVr919xbazLYBqX6FnkX4Di0jaDMK5XcjjK/uMU1odiiLeBEBo1d4T0QdMpEy0+ jyRLvCO5FOguVsjRyr9wfw+FXVvtK8yRjlIgxjLl4T5SjDwS6xvUTOy+7mS8vVjAOD0E i0U+/oZbVJStryCqdcWS1IPMJ6LO1hd+h0tg19xsC+hxEoGXXHM4wkjUjCorO4cbz+07 kzAti+LbC795GgUaDq+NPOWfVtnnMrbTZOKP1OtIeGSG5vR++4hhjmcsOenftYptiTvS oqhw== X-Received: by 10.112.78.4 with SMTP id x4mr309143lbw.81.1388079054018; Thu, 26 Dec 2013 09:30:54 -0800 (PST) MIME-Version: 1.0 Sender: royce.williams@gmail.com Received: by 10.112.163.100 with HTTP; Thu, 26 Dec 2013 09:30:33 -0800 (PST) In-Reply-To: <20131226174629.241d7f90@bsd64.grem.de> References: <52BBC4F3.2050508@dougbarton.us> <1388040674.3771.27.camel@eva02.mbsd> <52BBD2FC.2070405@dougbarton.us> <20131226100851.GD40122@ithaqua.etoilebsd.net> <20131226162331.GO40122@ithaqua.etoilebsd.net> <20131226174629.241d7f90@bsd64.grem.de> From: Royce Williams Date: Thu, 26 Dec 2013 08:30:33 -0900 X-Google-Sender-Auth: SzkSg1geu0YTd0DVQ_xQT_elHdc Message-ID: Subject: Re: WITHOUT_NLS is deprecated use NLS option instead To: FreeBSD Mailing List Content-Type: text/plain; charset=ISO-8859-1 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Dec 2013 17:30:56 -0000 On Thu, Dec 26, 2013 at 7:46 AM, Michael Gmelin wrote: > Adding a (shortened, so easy to type) URL pointing to the wiki or > whatever resource describing why this happened could be useful (not just > for this, but for all of these deprecation warnings, so users > understand the rationale behind them). Yes! +10 (not a typo). Please cache more breadcrumbs so that others can use them. For example, I'm getting this now: pkg: PACKAGESITE in pkg.conf is deprecated. Please create a repository configuration file ... but as you can see in this thread, people have been looking for breadcrumbs and having trouble finding anything useful: https://forums.freebsd.org/viewtopic.php?t=43506 ... especially when this message appears even if PACKAGESITE doesn't actually appear in pkg.conf. Royce