From owner-freebsd-ports@FreeBSD.ORG Sat Sep 10 23:03:02 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8B001106564A for ; Sat, 10 Sep 2011 23:03:02 +0000 (UTC) (envelope-from code@apotheon.net) Received: from oproxy5-pub.bluehost.com (oproxy5.bluehost.com [IPv6:2605:dc00:100:2::a5]) by mx1.freebsd.org (Postfix) with SMTP id 484F88FC08 for ; Sat, 10 Sep 2011 23:03:02 +0000 (UTC) Received: (qmail 17652 invoked by uid 0); 10 Sep 2011 23:03:01 -0000 Received: from unknown (HELO box543.bluehost.com) (74.220.219.143) by cpoproxy2.bluehost.com with SMTP; 10 Sep 2011 23:03:01 -0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=apotheon.net; s=default; h=In-Reply-To:Content-Type:Mime-Version:References:Message-ID:Subject:To:From:Date; bh=TG+hgYQ1eQo9GDn2DgjbnRSEkMLQdvxsrN4JHATDCVY=; b=YuEnGK9KRCGohKvvvQGqs6Y8j+B7YKNIOLQ3G9WMdoYh5OwRB3+FqHaGyx9lsb+Uxdc3cqXrT3bn0dEcea2ZR4Cdw4BMl9ohThQKXeKn9udsAm7+yBxYy/o9YaVdKuso; Received: from c-24-8-180-234.hsd1.co.comcast.net ([24.8.180.234] helo=kukaburra.hydra) by box543.bluehost.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.76) (envelope-from ) id 1R2WZg-0004TO-OV for freebsd-ports@freebsd.org; Sat, 10 Sep 2011 17:03:01 -0600 Received: by kukaburra.hydra (sSMTP sendmail emulation); Sat, 10 Sep 2011 16:44:05 -0600 Date: Sat, 10 Sep 2011 16:44:05 -0600 From: Chad Perrin To: freebsd-ports@freebsd.org Message-ID: <20110910224405.GA24612@guilt.hydra> Mail-Followup-To: freebsd-ports@freebsd.org References: <4E67935C.6080702@aldan.algebra.com> <4E68AC85.4060705@icritical.com> <4E68F34C.6090504@FreeBSD.org> <20110909040954.17733a4e@cox.net> <4E6A476D.7090800@gmx.de> <4e6b6f41.hI3BQG0rpsUjddcD%perryh@pluto.rain.com> <4E6B374C.5040302@gmx.de> <20110910161736.GB23457@guilt.hydra> <4E6BCADF.3080909@gmx.de> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="k1lZvvs/B4yU6o8G" Content-Disposition: inline In-Reply-To: <4E6BCADF.3080909@gmx.de> User-Agent: Mutt/1.4.2.3i X-Identified-User: {2737:box543.bluehost.com:apotheon:apotheon.org} {sentby:smtp auth 24.8.180.234 authed with ren@apotheon.org} Subject: Re: sysutils/cfs X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 Sep 2011 23:03:02 -0000 --k1lZvvs/B4yU6o8G Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Sep 10, 2011 at 10:38:55PM +0200, Matthias Andree wrote: > Am 10.09.2011 18:17, schrieb Chad Perrin: > > On Sat, Sep 10, 2011 at 12:09:16PM +0200, Matthias Andree wrote: > >> > >> On the other hand, you're pointing out a problem of dead ports in the > >> first place: if the API of (usually library) port Y changes, and port X > >> is unmaintained, that's typically a situation where port X needs to be > >> deprecated and removed (and also will no longer build and/or work). > >=20 > > I want to understand all the reasoning behind this stuff. Please expla= in > > the reason that library Y changing means that dependent port X should be > > deprecated and removed, regardless of whether it no longer builds and/or > > works. Note that I'm working on the assumption that your assertion it > > should be deprecated and removed does not rely on it no longer building > > and/or working because of the way you mentioned no longering building > > and/or working as a parenthetical addendum rather than a condition of > > deprecation and removal. >=20 > I suppose you missed the meaning of "if the API of port Y changes". > API =3D application programming interface. This implies that either the > application no longer builds, or it is known that it would behave > inappropriately with the new library (because semantics changed). That would have been an unwarranted assumption. If the API changes, it might mean a couple of changes were made -- and they do not affect the parts of the API that port X uses. I chose to take what you said at face value, rather than make a bunch of assumptions about it. Thanks for clearing up your intended meaning, though. --=20 Chad Perrin [ original content licensed OWL: http://owl.apotheon.org ] --k1lZvvs/B4yU6o8G Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (FreeBSD) iEYEARECAAYFAk5r6DUACgkQ9mn/Pj01uKVWIgCg3HT6p66wo1nOVJ48FeV8RPqE U34AoKW+Jrr7KdtqdqOuJEODC96L0RTK =3znB -----END PGP SIGNATURE----- --k1lZvvs/B4yU6o8G--