From owner-freebsd-emulation@FreeBSD.ORG Fri Jan 17 09:10:01 2014 Return-Path: Delivered-To: vbox@smarthost.ysv.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 6B02EC65 for ; Fri, 17 Jan 2014 09:10:01 +0000 (UTC) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 5596B1E92 for ; Fri, 17 Jan 2014 09:10:01 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id s0H9A1NT015874 for ; Fri, 17 Jan 2014 09:10:01 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.7/8.14.7/Submit) id s0H9A1fK015871; Fri, 17 Jan 2014 09:10:01 GMT (envelope-from gnats) Date: Fri, 17 Jan 2014 09:10:01 GMT Message-Id: <201401170910.s0H9A1fK015871@freefall.freebsd.org> To: vbox@FreeBSD.org From: John Marino Subject: Re: ports/184296: devel/kBuild will not install on DragonFlyBSD due to hardcoded values in Makefile X-Mailman-Approved-At: Fri, 17 Jan 2014 12:42:38 +0000 X-BeenThere: freebsd-emulation@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list Reply-To: John Marino List-Id: Development of Emulators of other operating systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Jan 2014 09:10:01 -0000 The following reply was made to PR ports/184296; it has been noted by GNATS. From: John Marino To: bug-followup@FreeBSD.org, dlorch@gmail.com Cc: Subject: Re: ports/184296: devel/kBuild will not install on DragonFlyBSD due to hardcoded values in Makefile Date: Fri, 17 Jan 2014 10:08:22 +0100 I think it should handled in ports. 1) There are many ports that have similar code 2) FreeBSD understands DPorts exists and that DragonFly now uses ports, and that ports benefits from having multiple platforms use it, as well as the additional ports developers it brings. 3) Related to 2), especially when the changes are trivial, the ports are being modified to support multiple platforms. The case is the opposite; hundreds of patches and diffs in DPorts need to be pushed to ports (in many case they solve problems on FreeBSD too, not just DragonFly support), but there simply isn't the manpower to do it all at once. This is a trivial one-liner that has zero effect on FreeBSD and fixes DragonFly, so yes it should be changed at ports level. John