Date: Thu, 26 Dec 2013 18:30:07 +0100 From: Matthias Andree <matthias.andree@gmx.de> To: FreeBSD Ports <freebsd-ports@freebsd.org> Subject: Re: Updating CUPS Message-ID: <01418a96-df39-4a66-8ff6-004c67879290@email.android.com> In-Reply-To: <20131226065451.745a0c55@scorpio> References: <20131224154419.1b87ef83@scorpio> <fe29d3d0-4035-4a66-860e-35a6f795ce32@email.android.com> <20131226065451.745a0c55@scorpio>
next in thread | previous in thread | raw e-mail | index | archive | help
Jerry <jerry@seibercom=2Enet> schrieb:
>On Wed, 25 Dec 2013 09:14:55 +010=
0, Matthias Andree stated:
>
>> Jerry <jerry@seibercom=2Enet> 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: <owner-freebsd-ports@FreeBSD.ORG>
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 <freebsd-ports@freebsd.org>; 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 <freebsd-ports@freebsd.org>; Thu, 26 Dec 2013 17:30:55 +0000 (UTC)
Received: by mail-lb0-f176.google.com with SMTP id l4so3758133lbv.21
for <freebsd-ports@freebsd.org>; 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>
<alpine.BSF.2.00.1312260916440.24463@wonkity.com>
<20131226162331.GO40122@ithaqua.etoilebsd.net>
<alpine.BSF.2.00.1312260925550.24463@wonkity.com>
<20131226174629.241d7f90@bsd64.grem.de>
From: Royce Williams <royce@tycho.org>
Date: Thu, 26 Dec 2013 08:30:33 -0900
X-Google-Sender-Auth: SzkSg1geu0YTd0DVQ_xQT_elHdc
Message-ID: <CA+E3k939S-FZArFZSKyV2C+7Bs=t56dTY1h_Jw1+TjMCnTUEuw@mail.gmail.com>
Subject: Re: WITHOUT_NLS is deprecated use NLS option instead
To: FreeBSD Mailing List <freebsd-ports@freebsd.org>
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 <freebsd-ports.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-ports>,
<mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports/>;
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
<mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 26 Dec 2013 17:30:56 -0000
On Thu, Dec 26, 2013 at 7:46 AM, Michael Gmelin <freebsd@grem.de> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?01418a96-df39-4a66-8ff6-004c67879290>