From owner-freebsd-ports@FreeBSD.ORG Mon Aug 20 10:15:23 2012 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id AA7A7106564A; Mon, 20 Aug 2012 10:15:23 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from mail.zoral.com.ua (mx0.zoral.com.ua [91.193.166.200]) by mx1.freebsd.org (Postfix) with ESMTP id 3FF768FC08; Mon, 20 Aug 2012 10:15:21 +0000 (UTC) Received: from skuns.kiev.zoral.com.ua (localhost [127.0.0.1]) by mail.zoral.com.ua (8.14.2/8.14.2) with ESMTP id q7KAFNBQ013472; Mon, 20 Aug 2012 13:15:23 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.14.5/8.14.5) with ESMTP id q7KAFB9x085727; Mon, 20 Aug 2012 13:15:11 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.14.5/8.14.5/Submit) id q7KAFBNS085726; Mon, 20 Aug 2012 13:15:11 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Mon, 20 Aug 2012 13:15:10 +0300 From: Konstantin Belousov To: Juergen Lock Message-ID: <20120820101510.GJ33100@deviant.kiev.zoral.com.ua> References: <20120813211109.GA71682@triton8.kn-bremen.de> <20120813214651.GA72570@triton8.kn-bremen.de> <5029D6AE.4050205@gwdg.de> <20120814114214.GB94259@triton8.kn-bremen.de> <502A8206.4090505@gwdg.de> <20120814192453.GA8026@triton8.kn-bremen.de> <502AAD0E.2070909@FreeBSD.org> <20120815120143.GB33206@triton8.kn-bremen.de> <20120818204510.GA70765@triton8.kn-bremen.de> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="rmUrFcWP4LYae1gV" Content-Disposition: inline In-Reply-To: <20120818204510.GA70765@triton8.kn-bremen.de> User-Agent: Mutt/1.4.2.3i X-Virus-Scanned: clamav-milter 0.95.2 at skuns.kiev.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=-4.0 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on skuns.kiev.zoral.com.ua Cc: FreeBSD Ports , freebsd-multimedia@freebsd.org, freebsd-ports@freebsd.org, Kevin Oberman , kan@freebsd.org Subject: Re: __FreeBSD_version bump? (was: Re: vlc 2.0.3 ProjectM path fix) 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: Mon, 20 Aug 2012 10:15:23 -0000 --rmUrFcWP4LYae1gV Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Aug 18, 2012 at 10:45:10PM +0200, Juergen Lock wrote: > On Wed, Aug 15, 2012 at 10:09:59AM -0700, Kevin Oberman wrote: > > On Wed, Aug 15, 2012 at 5:01 AM, Juergen Lock = wrote: > > > On Tue, Aug 14, 2012 at 09:54:54PM +0200, Olli Hauer wrote: > > >> ... > > >> >> I think I got it: It is only a problem of configuring in the runn= ing > > >> >> vlc. You have to set the right path under > > >> >> 'Settings','All','Audio','Visualizing','projectM'. That's all ;-) > > >> >> > > >> > Aah-haah! :) I've fixed the default paths and made a new patch: > > >> > > > >> > http://people.freebsd.org/~nox/tmp/vlc-2.0.3-010.patch > > >> > > > >> > > >> > > >> >From your patch: > > >> > workaround is to deinstall the old vlc-1.x version before building > > >> > the new one. > > >> > > >> What about a conflict line ? > > >> CONFLICTS_BUILD=3D${PORTNAME}-1.* > > >> > > >> This allows users to fetch the source but they have to deinstall the > > >> old version before building the new one. > > > > > > Hm well the rtld bug this workaround is for only affects the > > > pulseaudio and notify knobs, and the workaround doesn't work for > > > the notify knob so it would only cover half the cases, and also > > > checking if this is needed in the port would require a > > > __FreeBSD_version bump which is probably overkill for this bug. > >=20 > > And why is it overkill? I regularly see comments about not wanting to > > bump __FreeBSD_version, but it's just an integer (though presented as > > a fixed-point fraction). There is no shortage and I never have > > understood why people are so hesitant to change it when there is a > > real, even if fairly small benefit from the bump. >=20 > Hmm. Alexander, what do you think? Not being Alexander, but appeared on Cc:. IMO, bumping __FreeBSD_version should not be done frivolous, and routine bug fixes are definitely not the good reason to bump. For one, users of HEAD or stable are assumed to run tip of the branch. If you want defined point of the branch, use release. With this POV, the usefulness of the bump for bug fix is only a week or two. Second, bump of __FreeBSD_version signifies major incompatibility between pre-bumped tree and current one. In the kernel, each bump of version in HEAD means that new modules cannot be loaded into new kernel. Bumping for bug fixes is a misuse of the mechanism which was put there to provide information about major changes in system. For small or detectable items, use autoconf-like runtime (or build-time *) tests. * - Usually, the tests must be run-time, and not build-time. This bug is greatly amplified by use of __FreeBSD_version. The case that initiated the discussion is probably the first time I ever saw the when build-time test makes some sense. --rmUrFcWP4LYae1gV Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (FreeBSD) iEYEARECAAYFAlAyDi4ACgkQC3+MBN1Mb4jqTQCgrqDlPFrRT0JaibAqDH7esjec lbAAn0ytBiCcX9mZsb3lNqoHKR19tQGz =4gBI -----END PGP SIGNATURE----- --rmUrFcWP4LYae1gV--