From owner-freebsd-arch@freebsd.org Sun Apr 16 20:21:38 2017 Return-Path: Delivered-To: freebsd-arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 75B63D410C9 for ; Sun, 16 Apr 2017 20:21:38 +0000 (UTC) (envelope-from bapt@FreeBSD.org) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 651B76C1 for ; Sun, 16 Apr 2017 20:21:38 +0000 (UTC) (envelope-from bapt@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id 61A50D410C8; Sun, 16 Apr 2017 20:21:38 +0000 (UTC) Delivered-To: arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 61561D410C7 for ; Sun, 16 Apr 2017 20:21:38 +0000 (UTC) (envelope-from bapt@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 45C316C0 for ; Sun, 16 Apr 2017 20:21:38 +0000 (UTC) (envelope-from bapt@FreeBSD.org) Received: by freefall.freebsd.org (Postfix, from userid 1235) id 756A8788; Sun, 16 Apr 2017 20:21:37 +0000 (UTC) Date: Sun, 16 Apr 2017 22:21:37 +0200 From: Baptiste Daroussin To: arch@FreeBSD.org Subject: modules finding order Message-ID: <20170416202137.5x4vegfnm2pvkn6t@ivaldir.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="vkx5rhddyn7egncs" Content-Disposition: inline User-Agent: NeoMutt/20170306 (1.8.0) X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 Apr 2017 20:21:38 -0000 --vkx5rhddyn7egncs Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Hi all, I would like to change in FreeBSD 12 at least the default order the modules are found/look up. For now the modules are loaded from /boot/kernel first then if not found, checked from /boot/modules. I think we should revert that to /boot/modules first then /boot/kernel. The main reason being to simplify multiple things: 1/ If one needs to change a module (like backporting) I could install it from package and it would take precedent from the one provided by the default kernel I'm using 2/ As a hacker I could build my own version of a given module and install it in /boot/modules I won't overwrite the default kernel module 3/ as a port maintainer I could provide my own version of the module that would take precedence over the one provided by the kernel. As it is a change in the default behaviour I would only do it for 12 (beside I would love to do it in earlier version :D) Anyone has an opinion on the subject? Best regards, Bapt --vkx5rhddyn7egncs Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEgOTj3suS2urGXVU3Y4mL3PG3PloFAljz0ksACgkQY4mL3PG3 PlrhEw//WYW9kQiQ9gyYjYjZiX/pjnpW+oWH51+ZsKfKh4F7m7WTZdtbKH5n087d 27DTTh2/7YWo8qV/VGd+fn8tZybvyONJBQBThY8k/vSPRmsE88KoZ767RgTZ5ox/ EBjHCm4k0EdqmiYtXNj3mt5Qc8/KswP1yac0ldkQWJTip+ORcGrnanAlBzP3+Z2x +au+Bjj5zcfcgs1bn5wXRc/sKOtlDeGOZTiHZYRY1jRjpDgw6tzU0eOpyM6G40/U P3o8kZ7/VIYAFwwDQsYc85NWLgzwwwX3tks1S5QhPCEOWdy3r7FvQEiotK7+ICSS zgnfpyA+h9elBj5nRjPc6/HYVEPP2Ti/Qox0CpeRV6jzXX7orMVI8USXuWDf08ui wzLxkaN4f0k4kCbKmbhLQj8RmCwlOyUcgb1w+5yMjLuc88v00lKJkQXoVePksGET 9C5coFTrerj6j1sdcFMG+QNCechyG/CBv1ViSF3D/2RN0bYds0JQqbjZJFJmj5YL sRfrte2Zi8aZ7A7gVBnwCThOdL+0HXVI9WSoaifCQPN6/pVdAPQfyZjbIoMvLooh NK1SzIQhR3d1++eIw68p2qg+ERskG0IJxlgKfhhdDc8Y4xEeHKus8NQgSVeTthvH 8Q5rZcELuTH+nAQx5vdFCA8VdWy6DeiOWxk2TnOAoW0Hx7UYhNc= =J9If -----END PGP SIGNATURE----- --vkx5rhddyn7egncs-- From owner-freebsd-arch@freebsd.org Sun Apr 16 22:12:55 2017 Return-Path: Delivered-To: freebsd-arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 08651D406DE for ; Sun, 16 Apr 2017 22:12:55 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id DBDDE259 for ; Sun, 16 Apr 2017 22:12:54 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id DB273D406DD; Sun, 16 Apr 2017 22:12:54 +0000 (UTC) Delivered-To: arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D911FD406DA for ; Sun, 16 Apr 2017 22:12:54 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: from mail-pf0-x22b.google.com (mail-pf0-x22b.google.com [IPv6:2607:f8b0:400e:c00::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id AAAE6257; Sun, 16 Apr 2017 22:12:54 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: by mail-pf0-x22b.google.com with SMTP id c198so58199062pfc.1; Sun, 16 Apr 2017 15:12:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=+g9MXKwclNbrhW7O65hJOI5lsFFwuM4b6LOBd9YwBOM=; b=mIFB4M9SxBOC5s/CZOpPjPO41RZJVB/vha7IsEYBE6LicmKwMZ267jPNeduqUiuZpQ 0uRGiktQqEOnZZ4yccT4p4g6Wc9905RJk4oUSUAur40dR4jRyNhSAsai4eycIDSUjVJg UBrO4zsO7vvtJ5LWCBeb5BJcpCbtEjs45XTixlIYHAPuEhwFFKWeSb1CnVluXLdSiju2 cx29TCGmly8V1o0hLpxo7jla6QBJausSKx7Da6stsNa2G1CJ31x6uhIfno/abtkeLnQw azffezYJIUzkD861UQrHImahDKbGmyIXgniuOHlqymNnEFvCdmxM3GkCTz8yShyDLZKf i6BA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:date:from:to:cc:subject:message-id :references:mime-version:content-disposition:in-reply-to:user-agent; bh=+g9MXKwclNbrhW7O65hJOI5lsFFwuM4b6LOBd9YwBOM=; b=T79H7D5F9ObDS2W7iTLDehilgWwO4F/wrO47Gp/8FzFs7wPIz1MVsHpUhM8eFM76XF I3eGElwACbSvRPWsQn80EG064V7NigtCxJbobvguSxpyKK179PYT9SwcbneTJodusnM+ hW2sWY5c3EjhwhW0WR7P3CZhcGNqxoTwuk3E07abTnDaJ1q2d++UHUV5KPKbzxFVJS1A N5K5cwFNIYxl0yehWUTNryDUTKRMFDa2VEtPcmUnIw5znkDgevEL3+812D9u9GpjoBi8 7HuW+BeonneEvhpOqFHPrqH6Zl5dLYdSTxCNjOaRfvUTPmmUYyCoqrSEpPpLeunGgPgm KBTQ== X-Gm-Message-State: AN3rC/5lVAx8o6ejATsEHFUBJFxJ+seiKe1sBjgpdm875ygUc+tzwvuH oT4AZ3u5IvQ89ctg X-Received: by 10.84.179.193 with SMTP id b59mr11875665plc.56.1492380774014; Sun, 16 Apr 2017 15:12:54 -0700 (PDT) Received: from raichu ([2604:4080:1102:0:ca60:ff:fe9d:3963]) by smtp.gmail.com with ESMTPSA id w3sm13916256pfw.15.2017.04.16.15.12.53 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 16 Apr 2017 15:12:53 -0700 (PDT) Sender: Mark Johnston Date: Sun, 16 Apr 2017 15:12:49 -0700 From: Mark Johnston To: Baptiste Daroussin Cc: arch@FreeBSD.org Subject: Re: modules finding order Message-ID: <20170416221249.GA11628@raichu> References: <20170416202137.5x4vegfnm2pvkn6t@ivaldir.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170416202137.5x4vegfnm2pvkn6t@ivaldir.net> User-Agent: Mutt/1.8.0 (2017-02-23) X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 Apr 2017 22:12:55 -0000 On Sun, Apr 16, 2017 at 10:21:37PM +0200, Baptiste Daroussin wrote: > Hi all, > > I would like to change in FreeBSD 12 at least the default order the modules are > found/look up. > > For now the modules are loaded from /boot/kernel first then if not found, > checked from /boot/modules. > > I think we should revert that to /boot/modules first then /boot/kernel. > > The main reason being to simplify multiple things: > 1/ If one needs to change a module (like backporting) I could install it from > package and it would take precedent from the one provided by the default kernel > I'm using > 2/ As a hacker I could build my own version of a given module and install it in > /boot/modules I won't overwrite the default kernel module This complements r299393. Since that revision went in I've confused myself several times by building and installing a module from sys/modules, and then forgetting to explicitly kldload from /boot/modules, so I instead get a stale copy. > 3/ as a port maintainer I could provide my own version of the module that would > take precedence over the one provided by the kernel. I think we would like this behaviour for a port that installs the DRM modules. > > As it is a change in the default behaviour I would only do it for 12 (beside I > would love to do it in earlier version :D) > > Anyone has an opinion on the subject? It seems reasonable to me. From owner-freebsd-arch@freebsd.org Mon Apr 17 06:58:35 2017 Return-Path: Delivered-To: freebsd-arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EEC20D41B03 for ; Mon, 17 Apr 2017 06:58:35 +0000 (UTC) (envelope-from gljennjohn@gmail.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id CC79F1E25 for ; Mon, 17 Apr 2017 06:58:35 +0000 (UTC) (envelope-from gljennjohn@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id C90B0D41B02; Mon, 17 Apr 2017 06:58:35 +0000 (UTC) Delivered-To: arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C70E4D41B01 for ; Mon, 17 Apr 2017 06:58:35 +0000 (UTC) (envelope-from gljennjohn@gmail.com) Received: from mail-wm0-x241.google.com (mail-wm0-x241.google.com [IPv6:2a00:1450:400c:c09::241]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4E6251E24; Mon, 17 Apr 2017 06:58:35 +0000 (UTC) (envelope-from gljennjohn@gmail.com) Received: by mail-wm0-x241.google.com with SMTP id q125so7401625wmd.3; Sun, 16 Apr 2017 23:58:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:cc:subject:message-id:in-reply-to:references:reply-to :mime-version:content-transfer-encoding; bh=L4YQOcljjGwAWDZGGjxy/0A0vfAp+j/IO8YSifXsiQM=; b=bBf03K/56K+esL5A3DA4Tjw8SCuW/Rt/EbaPFS5sSeCyo4ZZD0Xt8n74VMI5fsfvjE POiWJonQSwlSYOWP5ZY5EKglHzeR+o7l2HrmYReMP1vdNgMS87t6fLot1pqY9qJUox9D yUATBbbtfI65YsoEnJqxj9byc/Kd/cRR6LvVYz8ufj/Va9Zc9RqlscPcy2D7cnXMjCBw Uwo/k1XjfzmFYmWJWzg1pXaFu5DQfe/BtWhgGtcerIT6rytvPN6GgVgdaWAn7mRhdWrb a7TxvVDEliDmmNyTBVc+ebw6z7EN04cokcMkZtFXQLapZS61p39QHiZv5VOt1jbY3Nko n+SA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:in-reply-to :references:reply-to:mime-version:content-transfer-encoding; bh=L4YQOcljjGwAWDZGGjxy/0A0vfAp+j/IO8YSifXsiQM=; b=Nj9lJbFsbQiYHD25pb/dJZIYDjlFW4ltrgGNquPPa/L13B89PorNdQcZETEQ9iNx3k tC3y7QZVVQUIpKIc4tgUQQ81G40iFoDWYbUOWTDf6bknlT616SmBLylAfbDR0g23xbkg ujWiI4TFXijGCJ+VeOhbQEYjsHjHF3OcQz7/smkdz7E6SCILCe7YC+sQ/LxcWWILJ3rP rXH2Cjtck8QsRn5iZwhuULw6yuWzice4FvsYpNaaZNPcZ82e519+wvp8cyLVnQ8g0aFx kLFOfcypesoR0XOU/cfFQcUuZYlOVdTP5qPE42EEA5OuEVypZhMhyyEaZrnws96m0t9R fImg== X-Gm-Message-State: AN3rC/4JXDjRU440Vv0KgWGN4x8V2DK+KTrE39wTzSBxGdBwLwwwKPfm sHCkX66+vXkGAdGp X-Received: by 10.28.74.147 with SMTP id n19mr7930295wmi.86.1492412313192; Sun, 16 Apr 2017 23:58:33 -0700 (PDT) Received: from ernst.home (p4FCA618C.dip0.t-ipconnect.de. [79.202.97.140]) by smtp.gmail.com with ESMTPSA id o9sm9278673wmd.4.2017.04.16.23.58.31 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Sun, 16 Apr 2017 23:58:32 -0700 (PDT) Date: Mon, 17 Apr 2017 08:58:22 +0200 From: Gary Jennejohn To: Mark Johnston Cc: Baptiste Daroussin , arch@FreeBSD.org Subject: Re: modules finding order Message-ID: <20170417085822.0af03ceb@ernst.home> In-Reply-To: <20170416221249.GA11628@raichu> References: <20170416202137.5x4vegfnm2pvkn6t@ivaldir.net> <20170416221249.GA11628@raichu> Reply-To: gljennjohn@gmail.com X-Mailer: Claws Mail 3.14.1 (GTK+ 2.24.31; amd64-portbld-freebsd12.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Apr 2017 06:58:36 -0000 On Sun, 16 Apr 2017 15:12:49 -0700 Mark Johnston wrote: > On Sun, Apr 16, 2017 at 10:21:37PM +0200, Baptiste Daroussin wrote: > > Hi all, > > > > I would like to change in FreeBSD 12 at least the default order the modules are > > found/look up. > > > > For now the modules are loaded from /boot/kernel first then if not found, > > checked from /boot/modules. > > > > I think we should revert that to /boot/modules first then /boot/kernel. > > > > The main reason being to simplify multiple things: > > 1/ If one needs to change a module (like backporting) I could install it from > > package and it would take precedent from the one provided by the default kernel > > I'm using > > 2/ As a hacker I could build my own version of a given module and install it in > > /boot/modules I won't overwrite the default kernel module > > This complements r299393. Since that revision went in I've confused myself > several times by building and installing a module from sys/modules, and > then forgetting to explicitly kldload from /boot/modules, so I > instead get a stale copy. > > > 3/ as a port maintainer I could provide my own version of the module that would > > take precedence over the one provided by the kernel. > > I think we would like this behaviour for a port that installs the DRM > modules. > > > > > As it is a change in the default behaviour I would only do it for 12 (beside I > > would love to do it in earlier version :D) > > > > Anyone has an opinion on the subject? > > It seems reasonable to me. > The problem I see with this is that the module under /boot/modules may have been generated against a /usr/src which is newer than what was used to generate the running kernel. In this case kldload should (I hope) fail. I regularly update /usr/src without making a new world or kernel. If kldload automatically falls back to trying /boot/kernel in this case then everything would be OK. If kldload does not or cannot retry then I would not consider this change a good idea. There's also the possibility that the module is loaded successfully, but at run time it fails due to missing functionality in the old kernel. I'm not sure that this could happen. -- Gary Jennejohn From owner-freebsd-arch@freebsd.org Mon Apr 17 19:10:12 2017 Return-Path: Delivered-To: freebsd-arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6DE3ED415B0 for ; Mon, 17 Apr 2017 19:10:12 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 4B5EA1FB0 for ; Mon, 17 Apr 2017 19:10:12 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id 4AB02D415AF; Mon, 17 Apr 2017 19:10:12 +0000 (UTC) Delivered-To: arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4A4DBD415AE for ; Mon, 17 Apr 2017 19:10:12 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: from mail-qk0-x241.google.com (mail-qk0-x241.google.com [IPv6:2607:f8b0:400d:c09::241]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 03D2E1FAF; Mon, 17 Apr 2017 19:10:12 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: by mail-qk0-x241.google.com with SMTP id p68so20712879qke.1; Mon, 17 Apr 2017 12:10:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=qGmKpq2VwDn628E4cgL2RNIWfD70iE86HLBUDc6muXQ=; b=QDvf0aZ2ef7P9qijvFREhbXB/J2BnSrbZXkrRsg4cWHGTe+QbG/7ONsbq4kfFy0Hyf 8PaHQs3hJt63AqBLjt7q31uOFVdv0DbpIhrX66WKCLNGSkxqsG4VhzA5gtRh7E1VIO24 JF3+VNz6U0AG/obXRsvAh1ktYt4VyAiE//TM/QBIPd76MWPJFHO9EfnjIob9W5+K2Lel +yVpcDCkom86KZpC1syxu+yNdRqHv72/et92iAtGbAQOA5f5TOECRsflHy5Rp3RhLDi6 IqRB7sM/sgvlTInNYekXVJ5XrZl0Y7wMMuQwiZ12HtsNDv07GIjQCiEhe1McTsyaaZc6 kuig== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:date:from:to:cc:subject:message-id :references:mime-version:content-disposition:in-reply-to:user-agent; bh=qGmKpq2VwDn628E4cgL2RNIWfD70iE86HLBUDc6muXQ=; b=DKT2csnqrQW7+qWZSBOHgLVq8hrMnOuVKwlTf74CMmX8pZRpVEBgmIvVAWErN1fL17 GVPHIjMM7pxRgbrdp0reGo/8+IbG2aoEq7KfbTj6pWPT0OYUO/lnN/mkiehNisOY44U+ MfXWm+5MFp0lRlnwzx4IkAzL6Oo+GUC3pMIZQGMg5huOUyX51Nv8twwnGh+CPihD2u5e QtTFDtgB++ksPbx1Wdfx7YI9bAqoba+RPxAcKLu2MGJ6DdICQjfGHF+ajs8t08FUt3xI sRJDAhu8CDbe6o9+2p3UywMnJohW014swtfywiHNqGzH33xDy1EzSrc2Fi+i7ub5ntIb eELg== X-Gm-Message-State: AN3rC/70gL+KxRTbfQ/aTPB4Ff6YknuC5yNS+h6v84uFyohLfrqVCE0Q AKqCrjnzTO8S8twb X-Received: by 10.55.192.143 with SMTP id v15mr9642136qkv.88.1492456211195; Mon, 17 Apr 2017 12:10:11 -0700 (PDT) Received: from wkstn-mjohnston.west.isilon.com (c-76-104-201-218.hsd1.wa.comcast.net. [76.104.201.218]) by smtp.gmail.com with ESMTPSA id t71sm7920992qki.8.2017.04.17.12.10.09 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 17 Apr 2017 12:10:10 -0700 (PDT) Sender: Mark Johnston Date: Mon, 17 Apr 2017 12:09:40 -0700 From: Mark Johnston To: Gary Jennejohn Cc: Baptiste Daroussin , arch@FreeBSD.org Subject: Re: modules finding order Message-ID: <20170417190940.GC18960@wkstn-mjohnston.west.isilon.com> References: <20170416202137.5x4vegfnm2pvkn6t@ivaldir.net> <20170416221249.GA11628@raichu> <20170417085822.0af03ceb@ernst.home> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170417085822.0af03ceb@ernst.home> User-Agent: Mutt/1.8.0 (2017-02-23) X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Apr 2017 19:10:12 -0000 On Mon, Apr 17, 2017 at 08:58:22AM +0200, Gary Jennejohn wrote: > On Sun, 16 Apr 2017 15:12:49 -0700 > Mark Johnston wrote: > > On Sun, Apr 16, 2017 at 10:21:37PM +0200, Baptiste Daroussin wrote: > > > Hi all, > > > > > > I would like to change in FreeBSD 12 at least the default order the modules are > > > found/look up. > > > > > > For now the modules are loaded from /boot/kernel first then if not found, > > > checked from /boot/modules. > > > > > > I think we should revert that to /boot/modules first then /boot/kernel. > > > > The problem I see with this is that the module under > /boot/modules may have been generated against a /usr/src which is > newer than what was used to generate the running kernel. In this > case kldload should (I hope) fail. It may or may not; the load will fail if the running kernel's __FreeBSD_version does not match the value that the module was compiled with. If the __FreeBSD_version values match, then the module is in theory compatible with the running kernel and should just work. > I regularly update /usr/src without making a new world or kernel. > > If kldload automatically falls back to trying /boot/kernel in > this case then everything would be OK. If kldload does not or > cannot retry then I would not consider this change a good idea. I don't think there's any mechanism to fall back. A "kldload foo" from the command line will cause the kernel to try and load the first "foo.ko" found in the paths given by the kern.module_path sysctl value. If that fails, the kldload fails. I'm not sure how it works for modules loaded by loader(8). > > There's also the possibility that the module is loaded > successfully, but at run time it fails due to missing > functionality in the old kernel. I'm not sure that this could > happen. From owner-freebsd-arch@freebsd.org Wed Apr 19 05:39:34 2017 Return-Path: Delivered-To: freebsd-arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D999BD453F1 for ; Wed, 19 Apr 2017 05:39:34 +0000 (UTC) (envelope-from b.16012508@edmmessage.com) Received: from mail28.wt1.edmmessage.com (mail28.wt1.edmmessage.com [101.78.203.28]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id ED1F41718 for ; Wed, 19 Apr 2017 05:39:33 +0000 (UTC) (envelope-from b.16012508@edmmessage.com) Received: from 101.78.203.28 (mail28.wt1.edmmessage.com [101.78.203.28]) by mail28.wt1.edmmessage.com (Postfix) with ESMTP id 50A98218024 for ; Wed, 19 Apr 2017 13:39:32 +0800 (HKT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; t=1492580372; s=default; d=edmmessage.com; h=Date:From:Reply-To:To:Subject:MIME-Version:Content-Type:Content-Transfer-Encoding; bh=jTLYgoRUKykDYr82HJajB3ec7rl5HTgZHc6LQRXp19k=; b=mERWpBO314dqr+xrzPdvqch3tTvEjk3xxl69TiBuMaMqujBwJMWToNcqWeuHhJ9R 8zoymdo9CAp0YDBn9lQGO8422Ef3w5NftT+i28cZvfAim1vyTKTyDrtVXm6eiXtY7YI oZqQOu0VTwxVD9YedkvWwRmP1D9QYP0O1rPcA/O0= Date: Wed, 19 Apr 2017 13:39:32 +0800 (HKT) From: "jhie.powermax" Reply-To: "jhie.powermax" To: JHIE-07-YMLP Message-ID: <601389016.6598948.1492580372329.JavaMail.tomcat@wt2> Subject: eBIR FORMS and 2017 Tax Updates - May 5 Errors-To: b.16012508@edmmessage.com X-Content-ID: nEd7sLMsTUlbvTZiji+C3ficFQPFkTM4Vd/F7TljVDR3CEY4FnL9WzBcRS5SO+rC67hV7N25Yg9r3Z/RGpcu05+XXfslX0ARUrRu2QvdwDbcU0omG8K+ONQ1q4Mkx5na Feedback-ID: 816893694337805:691887480124289:008494288642614:edmmessage.com MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Apr 2017 05:39:34 -0000 From owner-freebsd-arch@freebsd.org Wed Apr 19 10:51:58 2017 Return-Path: Delivered-To: freebsd-arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6D670D44211 for ; Wed, 19 Apr 2017 10:51:58 +0000 (UTC) (envelope-from b.16012507@edmmessage.com) Received: from mail28.wt1.edmmessage.com (mail28.wt1.edmmessage.com [101.78.203.28]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 807EF16E6 for ; Wed, 19 Apr 2017 10:51:57 +0000 (UTC) (envelope-from b.16012507@edmmessage.com) Received: from 101.78.203.28 (mail28.wt1.edmmessage.com [101.78.203.28]) by mail28.wt1.edmmessage.com (Postfix) with ESMTP id CD63A205443 for ; Wed, 19 Apr 2017 18:51:55 +0800 (HKT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; t=1492599115; s=default; d=edmmessage.com; h=Date:From:Reply-To:To:Subject:MIME-Version:Content-Type:Content-Transfer-Encoding; bh=u3LMXQ9zV7SZdyn6mgnzU2CNivQK1JdOyZJ/lW4mAvg=; b=HJ5KGeKcoC2g/vAhDGs03kT3vFcsRvMV7B4ENQ+lME2kqWRyesHNhymzoaiqm01c XDAim3UfgJnPb2vd5VzvajVy2TlZLQCUrj25EqZGkuRrhD0avnSOIVZR/fpU/77KTg8 CVvEJDGaenxI8ThpzgEPGl71kR7WCnKVgrpkMIZM= Date: Wed, 19 Apr 2017 18:51:55 +0800 (HKT) From: "jhie.powermax" Reply-To: "jhie.powermax" To: JHIE-07-YMLP Message-ID: <240102315.6736372.1492599115840.JavaMail.tomcat@wt2> Subject: LAST CALL: Maximizing Productivity in Warehouse Management - May 4 Errors-To: b.16012507@edmmessage.com X-Content-ID: b9oJqFZalmIvJu28ix9Ap3pQiG0tXKRQVd/F7TljVDR3CEY4FnL9WzBcRS5SO+rC67hV7N25Yg9r3Z/RGpcu05+XXfslX0ARUrRu2QvdwDbcU0omG8K+ONQ1q4Mkx5na Feedback-ID: 816893694337805:940156826202516:008494288642614:edmmessage.com MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Apr 2017 10:51:58 -0000 From owner-freebsd-arch@freebsd.org Thu Apr 20 21:18:21 2017 Return-Path: Delivered-To: freebsd-arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4D8D5D48356 for ; Thu, 20 Apr 2017 21:18:21 +0000 (UTC) (envelope-from kwm@FreeBSD.org) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 37AEAAE0 for ; Thu, 20 Apr 2017 21:18:21 +0000 (UTC) (envelope-from kwm@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id 31188D48354; Thu, 20 Apr 2017 21:18:21 +0000 (UTC) Delivered-To: arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3065FD48350; Thu, 20 Apr 2017 21:18:21 +0000 (UTC) (envelope-from kwm@FreeBSD.org) Received: from smtpq6.tb.mail.iss.as9143.net (smtpq6.tb.mail.iss.as9143.net [212.54.42.169]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 96C58ADD; Thu, 20 Apr 2017 21:18:17 +0000 (UTC) (envelope-from kwm@FreeBSD.org) Received: from [212.54.42.118] (helo=lsmtp4.tb.mail.iss.as9143.net) by smtpq6.tb.mail.iss.as9143.net with esmtp (Exim 4.86_2) (envelope-from ) id 1d1JSx-0000mZ-1e; Thu, 20 Apr 2017 23:18:15 +0200 Received: from f49083.upc-f.chello.nl ([80.56.49.83] helo=[192.168.1.74]) by lsmtp4.tb.mail.iss.as9143.net with esmtp (Exim 4.86_2) (envelope-from ) id 1d1JSw-0005du-Tm; Thu, 20 Apr 2017 23:18:15 +0200 Message-ID: <1492723094.55896.22.camel@FreeBSD.org> Subject: Re: manpath change for ports ? From: Koop Mast To: Baptiste Daroussin , arch@FreeBSD.org, ports@FreeBSD.org Date: Thu, 20 Apr 2017 23:18:14 +0200 In-Reply-To: <20170306235610.cmpxk27jhoafel6l@ivaldir.net> References: <20170306235610.cmpxk27jhoafel6l@ivaldir.net> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.18.5.1 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: 8bit X-SourceIP: 80.56.49.83 X-Ziggo-spambar: / X-Ziggo-spamscore: 0.0 X-Ziggo-spamreport: CMAE Analysis: v=2.2 cv=C/qZ8UH+ c=1 sm=1 tr=0 a=06UDlCbfTTtHZh+D0N39nQ==:17 a=IkcTkHD0fZMA:10 a=AzvcPWV-tVgA:10 a=GUOmPLy3Ybawj284_7AA:9 a=QEXdDO2ut3YA:10 none X-Ziggo-Spam-Status: No X-Spam-Status: No X-Spam-Flag: No X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Apr 2017 21:18:21 -0000 On Tue, 2017-03-07 at 00:56 +0100, Baptiste Daroussin wrote: > Hi all, > > I would like to propose a change in the localbase hier for ports > > I think we should add /usr/local/share/man in the manpath along with > at first > and maybe instead of in long term. > > The reason is: > - /usr/local/share/man seems more consistent to me with base which > have: >   /usr/share/man > - It will remove lots of patches from the ports tree where were we > need to patch >   upstream build system to install in a non usual path. > > My proposal is to add to the manpath /usr/local/share/man in default > man(1) > command in FreeBSD 12 (MFCed to 11-STABLE) > > and either provide an errata for 11.0/10.3 or a > /usr/local/etc/man.d/something.conf via a port or something like that > for those > two, what do you think? > > For the same reason I would like to allow porters to stop patching > (with pathfix > or anything else) the path for pkgconfig files and allow > /usr/local/lib/pkgconfig along with the current > /usr/local/libdata/pkgconfig:/usr/libdata/pkgconfig > > Which will also remove tons of hacks from the ports tree. > > What do you think? > > Best regards, > Bapt Hello, I recently committed the USES for the meson build system to ports. This USES configures the meson build system with some default variables which includes the location of the man pages. This setting is just a flag to the meson command so it easy to change. Meson also handles the generation and installation of pkg-config files that a port wants. The problem is that this is handled by the script itself and there is no way to configure it, so we need to hack the meson port to change it from lib/pkg-config to libdata/pkg-config like we currently are using. (1) Or add a hack to meson.mk to move the pkg- config to the right location (evil++ imho). My point I want to make is that currently there is only 1 port build via the meson system (graphics/graphene). Should we change man/pkg- config file locations now, it very easy. If we want to change them later we will need to mass bump every meson build port. It is important to note that GStreamer and GNOME are moving over to using meson instead of autotools and that Wayland, Xorg en Mesa are exploring want is needed to make the switch. So I think it important that the decision what to do is done now and that we stick with it. Reading the rest of the thread it seems nobody is really against the proposed change of man and pkg-config path's. So how does one submit a policy change like this? I'm also not sure I'm the right person to push this, I just got back from a break and I don't want to really deal with something super high profile right away. -Koop (1) I would like to see lib/pkg-config back in the search path of pkgconf since that means I don't have to do a crash course python programming. From owner-freebsd-arch@freebsd.org Thu Apr 20 21:22:26 2017 Return-Path: Delivered-To: freebsd-arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EB76BD48B84 for ; Thu, 20 Apr 2017 21:22:26 +0000 (UTC) (envelope-from bapt@FreeBSD.org) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id D49C81BDA for ; Thu, 20 Apr 2017 21:22:26 +0000 (UTC) (envelope-from bapt@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id D114FD48B83; Thu, 20 Apr 2017 21:22:26 +0000 (UTC) Delivered-To: arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D09A0D48B81; Thu, 20 Apr 2017 21:22:26 +0000 (UTC) (envelope-from bapt@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [96.47.72.132]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 9009E1BD7; Thu, 20 Apr 2017 21:22:26 +0000 (UTC) (envelope-from bapt@FreeBSD.org) Received: by freefall.freebsd.org (Postfix, from userid 1235) id EE45A47B1; Thu, 20 Apr 2017 21:21:53 +0000 (UTC) Date: Thu, 20 Apr 2017 23:21:53 +0200 From: Baptiste Daroussin To: Koop Mast Cc: arch@FreeBSD.org, ports@FreeBSD.org, portmgr@FreeBSD.org Subject: Re: manpath change for ports ? Message-ID: <20170420212153.cawvn4xsxuwuebfu@ivaldir.net> References: <20170306235610.cmpxk27jhoafel6l@ivaldir.net> <1492723094.55896.22.camel@FreeBSD.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="akklfd3ecjwxpoxg" Content-Disposition: inline In-Reply-To: <1492723094.55896.22.camel@FreeBSD.org> User-Agent: NeoMutt/20170306 (1.8.0) X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Apr 2017 21:22:27 -0000 --akklfd3ecjwxpoxg Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Apr 20, 2017 at 11:18:14PM +0200, Koop Mast wrote: > On Tue, 2017-03-07 at 00:56 +0100, Baptiste Daroussin wrote: > > Hi all, > >=20 > > I would like to propose a change in the localbase hier for ports > >=20 > > I think we should add /usr/local/share/man in the manpath along with > > at first > > and maybe instead of in long term. > >=20 > > The reason is: > > - /usr/local/share/man seems more consistent to me with base which > > have: > > =A0 /usr/share/man > > - It will remove lots of patches from the ports tree where were we > > need to patch > > =A0 upstream build system to install in a non usual path. > >=20 > > My proposal is to add to the manpath /usr/local/share/man in default > > man(1) > > command in FreeBSD 12 (MFCed to 11-STABLE) > >=20 > > and either provide an errata for 11.0/10.3 or a > > /usr/local/etc/man.d/something.conf via a port or something like that > > for those > > two, what do you think? > >=20 > > For the same reason I would like to allow porters to stop patching > > (with pathfix > > or anything else) the path for pkgconfig files and allow > > /usr/local/lib/pkgconfig along with the current > > /usr/local/libdata/pkgconfig:/usr/libdata/pkgconfig > >=20 > > Which will also remove tons of hacks from the ports tree. > >=20 > > What do you think? > >=20 > > Best regards, > > Bapt >=20 > Hello, >=20 > I recently committed the USES for the meson build system to ports. This > USES configures the meson build system with some default variables > which includes the location of the man pages. This setting is just a > flag to the meson command so it easy to change. >=20 > Meson also handles the generation and installation of pkg-config files > that a port wants. The problem is that this is handled by the script > itself and there is no way to configure it, so we need to hack the > meson port to change it from lib/pkg-config to libdata/pkg-config like > we currently are using. (1) Or add a hack to meson.mk to move the pkg- > config to the right location (evil++ imho). >=20 > My point I want to make is that currently there is only 1 port build > via the meson system (graphics/graphene). Should we change man/pkg- > config file locations now, it very easy. If we want to change them > later we will need to mass bump every meson build port. It is important > to note that GStreamer and GNOME are moving over to using meson instead > of autotools and that Wayland, Xorg en Mesa are exploring want is > needed to make the switch. So I think it important that the decision > what to do is done now and that we stick with it. >=20 > Reading the rest of the thread it seems nobody is really against the > proposed change of man and pkg-config path's. So how does one submit a > policy change like this? I'm also not sure I'm the right person to push > this, I just got back from a break and I don't want to really deal with > something super high profile right away. >=20 > -Koop >=20 > (1) I would like to see lib/pkg-config back in the search path of > pkgconf since that means I don't have to do a crash course python > programming. Would be nice is portmgr can step on this, let's reduce this discussion for= now on pkgconf. Best regards, Bapt --akklfd3ecjwxpoxg Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEgOTj3suS2urGXVU3Y4mL3PG3PloFAlj5JnEACgkQY4mL3PG3 PloiNBAAvrZY2nONkMQTlWiOVr+3QBtR63PPEPFtzVBZnGpapQBQW8V/99n06gHV 9ibuniGCPqjqrpNWbPyKmAiX+D759UbfoqzYT3Cx+sz0v/SxUEn249p/eiHG3PTi EJ/vYIK76WeVCMLqmfXdy0Rdd09elWzW5A45oqRb8HCP0azAlmblcXz8a83rYME2 sf3ve1BgSsG/zvLCXvzdW5BcsX8FbasfDPEtMP1MRmRAxQaZnAeViViNBY+bQwAL moipmmtyrgbgVjLGGekfNdMvZnLuToVRfrf6otrQCj4G/VhnT8YnQ7yEAE9p6vh3 BCEAK/Rf2oz58NytEe2tyW9FjDyOJ9Ep/IhzQM1r/7pTe9cq4Fxv21qAXmiOltUB +y4cF+kSjKbOH8Nm9iUpO/CLr9Ceg7iWKWxvmsIPAXd9Ye5k6j6U4b2OIBLhFPz9 Wj72zr0UQr7Da7gaUBMzGYAJ5OXvGXA98/rQW2Oq9wLxZ16tt0PiGM+yRP39qPpu wEAvz3ZZG8/u1qnjSGk6Pv4Jv21XmAy3cFXlJbUmVwoK8bKb1DDw24g27B/IWYjT JNBlfG1Oq/SgQzCQaRbcXDLu2R1MjzrfxGgImUGXP1ZMGunvZFXB4VKbp+xdcmhl vnO0Gp6sGrJm5cStBPdd/rYPRDFb+PD8oJ1Dtna58Lcy/dCeqvA= =gOrr -----END PGP SIGNATURE----- --akklfd3ecjwxpoxg-- From owner-freebsd-arch@freebsd.org Thu Apr 20 22:13:55 2017 Return-Path: Delivered-To: freebsd-arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BFD42D48D14 for ; Thu, 20 Apr 2017 22:13:55 +0000 (UTC) (envelope-from mat@FreeBSD.org) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id A239F1DBC for ; Thu, 20 Apr 2017 22:13:55 +0000 (UTC) (envelope-from mat@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id 9EE39D48D12; Thu, 20 Apr 2017 22:13:55 +0000 (UTC) Delivered-To: arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9E63BD48D11; Thu, 20 Apr 2017 22:13:55 +0000 (UTC) (envelope-from mat@FreeBSD.org) Received: from prod2.absolight.net (mx3.absolight.net [IPv6:2a01:678:2:100::25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "plouf.absolight.net", Issuer "CAcert Class 3 Root" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 3BCBC1DBA; Thu, 20 Apr 2017 22:13:55 +0000 (UTC) (envelope-from mat@FreeBSD.org) Received: from prod2.absolight.net (localhost [127.0.0.1]) by prod2.absolight.net (Postfix) with ESMTP id 952E0BDC89; Fri, 21 Apr 2017 00:13:53 +0200 (CEST) Received: from atuin.in.mat.cc (atuin.in.mat.cc [79.143.241.205]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by prod2.absolight.net (Postfix) with ESMTPSA id 62A9FBDC85; Fri, 21 Apr 2017 00:13:53 +0200 (CEST) Subject: Re: manpath change for ports ? To: Baptiste Daroussin , Koop Mast Cc: arch@FreeBSD.org, ports@FreeBSD.org, portmgr@FreeBSD.org References: <20170306235610.cmpxk27jhoafel6l@ivaldir.net> <1492723094.55896.22.camel@FreeBSD.org> <20170420212153.cawvn4xsxuwuebfu@ivaldir.net> From: Mathieu Arnold Organization: Absolight / The FreeBSD Foundation Message-ID: Date: Fri, 21 Apr 2017 00:13:52 +0200 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:52.0) Gecko/20100101 Thunderbird/52.0.1 MIME-Version: 1.0 In-Reply-To: <20170420212153.cawvn4xsxuwuebfu@ivaldir.net> Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="6BetvbhbJJtKVL9x7EQK9wxNh1K9HmfI4" X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Apr 2017 22:13:55 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --6BetvbhbJJtKVL9x7EQK9wxNh1K9HmfI4 Content-Type: multipart/mixed; boundary="99btd0QpQ3QbTKV5eB4gnRJx9X1mfLF7K"; protected-headers="v1" From: Mathieu Arnold To: Baptiste Daroussin , Koop Mast Cc: arch@FreeBSD.org, ports@FreeBSD.org, portmgr@FreeBSD.org Message-ID: Subject: Re: manpath change for ports ? References: <20170306235610.cmpxk27jhoafel6l@ivaldir.net> <1492723094.55896.22.camel@FreeBSD.org> <20170420212153.cawvn4xsxuwuebfu@ivaldir.net> In-Reply-To: <20170420212153.cawvn4xsxuwuebfu@ivaldir.net> --99btd0QpQ3QbTKV5eB4gnRJx9X1mfLF7K Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Content-Language: fr Le 20/04/2017 =C3=A0 23:21, Baptiste Daroussin a =C3=A9crit : > On Thu, Apr 20, 2017 at 11:18:14PM +0200, Koop Mast wrote: >> On Tue, 2017-03-07 at 00:56 +0100, Baptiste Daroussin wrote: >>> Hi all, >>> >>> I would like to propose a change in the localbase hier for ports >>> >>> I think we should add /usr/local/share/man in the manpath along with >>> at first >>> and maybe instead of in long term. >>> >>> The reason is: >>> - /usr/local/share/man seems more consistent to me with base which >>> have: >>> /usr/share/man >>> - It will remove lots of patches from the ports tree where were we >>> need to patch >>> upstream build system to install in a non usual path. >>> >>> My proposal is to add to the manpath /usr/local/share/man in default >>> man(1) >>> command in FreeBSD 12 (MFCed to 11-STABLE) >>> >>> and either provide an errata for 11.0/10.3 or a >>> /usr/local/etc/man.d/something.conf via a port or something like that= >>> for those >>> two, what do you think? >>> >>> For the same reason I would like to allow porters to stop patching >>> (with pathfix >>> or anything else) the path for pkgconfig files and allow >>> /usr/local/lib/pkgconfig along with the current >>> /usr/local/libdata/pkgconfig:/usr/libdata/pkgconfig >>> >>> Which will also remove tons of hacks from the ports tree. >>> >>> What do you think? >>> >>> Best regards, >>> Bapt >> Hello, >> >> I recently committed the USES for the meson build system to ports. Thi= s >> USES configures the meson build system with some default variables >> which includes the location of the man pages. This setting is just a >> flag to the meson command so it easy to change. >> >> Meson also handles the generation and installation of pkg-config files= >> that a port wants. The problem is that this is handled by the script >> itself and there is no way to configure it, so we need to hack the >> meson port to change it from lib/pkg-config to libdata/pkg-config like= >> we currently are using. (1) Or add a hack to meson.mk to move the pkg-= >> config to the right location (evil++ imho). >> >> My point I want to make is that currently there is only 1 port build >> via the meson system (graphics/graphene). Should we change man/pkg- >> config file locations now, it very easy. If we want to change them >> later we will need to mass bump every meson build port. It is importan= t >> to note that GStreamer and GNOME are moving over to using meson instea= d >> of autotools and that Wayland, Xorg en Mesa are exploring want is >> needed to make the switch. So I think it important that the decision >> what to do is done now and that we stick with it. >> >> Reading the rest of the thread it seems nobody is really against the >> proposed change of man and pkg-config path's. So how does one submit a= >> policy change like this? I'm also not sure I'm the right person to pus= h >> this, I just got back from a break and I don't want to really deal wit= h >> something super high profile right away. >> >> -Koop >> >> (1) I would like to see lib/pkg-config back in the search path of >> pkgconf since that means I don't have to do a crash course python >> programming. > Would be nice is portmgr can step on this, let's reduce this discussion= for now > on pkgconf. I am waiting on an exp-run to fix this once and for all. https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D218067 When that is committed, anything can be added to the path pkgconfig searches, ports will always install it in the right place. --=20 Mathieu Arnold --99btd0QpQ3QbTKV5eB4gnRJx9X1mfLF7K-- --6BetvbhbJJtKVL9x7EQK9wxNh1K9HmfI4 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQJ8BAEBCgBmBQJY+TKhXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzQUI2OTc4OUQyRUQxMjEwNjQ0MEJBNUIz QTQ1MTZGMzUxODNDRTQ4AAoJEDpFFvNRg85IUh8P/Rs2SBNgcZ6POD8eHnfyEt1m kr6QUiQxOuYrb/SHk9HsnuugNxZ1CPnWOUEc65GlcN0iMgWnmbW6QuRbsXL/A1Yu ZwY6HwxEaHOUzL9HZ/MA8e3xOtSmLbRVut4Jy9m5v5VnKBqZeCDkS1WRIo3MfJNd pCBjEHZPUtR7Do0OglD7k/jzVgQqROBZpnh7R5Hy4EFsoR+zM0hqch0hPxeKiBx9 vK3wm11XLwNeeP/5MrI5pR8eLCZxhqXD7+ZjXmE/zlNu0vAMDh6h1gERtVxRzXOL JAMHve0xAe4INH852gTyUMSqEkbE9yBe8bdkImcjQlJchms/lp7nGFJiVBSEgXmW iYUPff07+cANergO4eW2Dogb2t0iFbj6UDMcD/J9xl7BIP5cE0Bmcop7VPR64n6q oY21DJnO2hbXo+t3L97sAzuvn0F2l2nh6H53cLQ7/747nkECuSFXEsJ2o4F1DuUn XTxA9ZsebrIS5ZAFQeOX2KLQfCJJYALO7d9BMPcgyyv45CSHA4uYfCMm0rSdymfc 1h2xKy/h0zo8pU1l3h0srghnrNOjbu8ipJ49eN3lyPaMLm7CrDy6KbYOAGTH4J3E RNNws88dMrF1+psFqK7l6ixQ+5JjF1Nn2Ic6bH5o1PWUhEHY7qOZPSkkxLQyOKWO dHZE+kE52tpZGni/MVpS =9jJR -----END PGP SIGNATURE----- --6BetvbhbJJtKVL9x7EQK9wxNh1K9HmfI4-- From owner-freebsd-arch@freebsd.org Thu Apr 20 22:16:33 2017 Return-Path: Delivered-To: freebsd-arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3AC79D48E32 for ; Thu, 20 Apr 2017 22:16:33 +0000 (UTC) (envelope-from bapt@FreeBSD.org) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 26CA29E for ; Thu, 20 Apr 2017 22:16:33 +0000 (UTC) (envelope-from bapt@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id 228B3D48E30; Thu, 20 Apr 2017 22:16:33 +0000 (UTC) Delivered-To: arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2210DD48E2F; Thu, 20 Apr 2017 22:16:33 +0000 (UTC) (envelope-from bapt@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0211D9D; Thu, 20 Apr 2017 22:16:33 +0000 (UTC) (envelope-from bapt@FreeBSD.org) Received: by freefall.freebsd.org (Postfix, from userid 1235) id 33DE455A8; Thu, 20 Apr 2017 22:16:32 +0000 (UTC) Date: Fri, 21 Apr 2017 00:16:31 +0200 From: Baptiste Daroussin To: Mathieu Arnold Cc: Koop Mast , ports@FreeBSD.org, arch@FreeBSD.org, portmgr@FreeBSD.org Subject: Re: manpath change for ports ? Message-ID: <20170420221631.yxukhuwo4tn7blte@ivaldir.net> References: <20170306235610.cmpxk27jhoafel6l@ivaldir.net> <1492723094.55896.22.camel@FreeBSD.org> <20170420212153.cawvn4xsxuwuebfu@ivaldir.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="sl34vmva77hxhbwl" Content-Disposition: inline In-Reply-To: User-Agent: NeoMutt/20170306 (1.8.0) X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Apr 2017 22:16:33 -0000 --sl34vmva77hxhbwl Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Apr 21, 2017 at 12:13:52AM +0200, Mathieu Arnold wrote: > Le 20/04/2017 =E0 23:21, Baptiste Daroussin a =E9crit : > > On Thu, Apr 20, 2017 at 11:18:14PM +0200, Koop Mast wrote: > >> On Tue, 2017-03-07 at 00:56 +0100, Baptiste Daroussin wrote: > >>> Hi all, > >>> > >>> I would like to propose a change in the localbase hier for ports > >>> > >>> I think we should add /usr/local/share/man in the manpath along with > >>> at first > >>> and maybe instead of in long term. > >>> > >>> The reason is: > >>> - /usr/local/share/man seems more consistent to me with base which > >>> have: > >>> /usr/share/man > >>> - It will remove lots of patches from the ports tree where were we > >>> need to patch > >>> upstream build system to install in a non usual path. > >>> > >>> My proposal is to add to the manpath /usr/local/share/man in default > >>> man(1) > >>> command in FreeBSD 12 (MFCed to 11-STABLE) > >>> > >>> and either provide an errata for 11.0/10.3 or a > >>> /usr/local/etc/man.d/something.conf via a port or something like that > >>> for those > >>> two, what do you think? > >>> > >>> For the same reason I would like to allow porters to stop patching > >>> (with pathfix > >>> or anything else) the path for pkgconfig files and allow > >>> /usr/local/lib/pkgconfig along with the current > >>> /usr/local/libdata/pkgconfig:/usr/libdata/pkgconfig > >>> > >>> Which will also remove tons of hacks from the ports tree. > >>> > >>> What do you think? > >>> > >>> Best regards, > >>> Bapt > >> Hello, > >> > >> I recently committed the USES for the meson build system to ports. This > >> USES configures the meson build system with some default variables > >> which includes the location of the man pages. This setting is just a > >> flag to the meson command so it easy to change. > >> > >> Meson also handles the generation and installation of pkg-config files > >> that a port wants. The problem is that this is handled by the script > >> itself and there is no way to configure it, so we need to hack the > >> meson port to change it from lib/pkg-config to libdata/pkg-config like > >> we currently are using. (1) Or add a hack to meson.mk to move the pkg- > >> config to the right location (evil++ imho). > >> > >> My point I want to make is that currently there is only 1 port build > >> via the meson system (graphics/graphene). Should we change man/pkg- > >> config file locations now, it very easy. If we want to change them > >> later we will need to mass bump every meson build port. It is important > >> to note that GStreamer and GNOME are moving over to using meson instead > >> of autotools and that Wayland, Xorg en Mesa are exploring want is > >> needed to make the switch. So I think it important that the decision > >> what to do is done now and that we stick with it. > >> > >> Reading the rest of the thread it seems nobody is really against the > >> proposed change of man and pkg-config path's. So how does one submit a > >> policy change like this? I'm also not sure I'm the right person to push > >> this, I just got back from a break and I don't want to really deal with > >> something super high profile right away. > >> > >> -Koop > >> > >> (1) I would like to see lib/pkg-config back in the search path of > >> pkgconf since that means I don't have to do a crash course python > >> programming. > > Would be nice is portmgr can step on this, let's reduce this discussion= for now > > on pkgconf. >=20 >=20 > I am waiting on an exp-run to fix this once and for all. >=20 > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D218067 >=20 > When that is committed, anything can be added to the path pkgconfig > searches, ports will always install it in the right place. >=20 Sorry but why? why not moving libdata/pkgconfig to lib/pkgconfig? what is t= he rationale? Bapt --sl34vmva77hxhbwl Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEgOTj3suS2urGXVU3Y4mL3PG3PloFAlj5MzkACgkQY4mL3PG3 PlphjRAA0m6+ToQaXkg+oY9oGAqr+E0XPmvE4ECiy4l0hKblbWHzE3xghFRuiSKa BfdO8DVJ28Eih6jBCJfktJTbwGZLU20R9EJWdM2rLNZICsHJ8cs4DhcP06GXNI4X QThKqMSvBQhlmH1gdgtm47i7sBQbBEU1k8FPsRBl1OgKsAXqXak9boTHbnhi7PGj u0Ves2vrrgtU4XgjQXxsot5IEZzoFzJROshVXGHmUNBD6rSzcps1pTLCtKK84BcW 4GztFkWvawxCVuixdmh/B95+lOBoPd57+QxcO8hFeGbmURCh8+GM5JGD7MkxUCs2 3qz5tcnLTBHlHABqaRKba/xWbj/KFZVPR8EM6+qlVX/M2GYgla5g4/GYUkuT05kw d/ofx8GTRnYWD9Zwwt3BO3JP5ngX7KalmEWwsFu5e/bgqMgimJdi05pRXZnjVSmm XAS7urTyF3J+Aeh/vO2Vd2EfRg2uDC+El7Ey1B7xiHFRQPFM68ahjtxu01hcn5lF X5qQ662nMANQQJ+u/nrEFLTOg7N/BMC46cKTjYOcxwRnueSa+VZV5I+EiKlLN6k0 jrtzb9w8uNgnICO8b1R1YW3QvQwqG/+xuz6qtSMkyQh1Nd1bPT1AUSXGUXC6TLWN 0G3IAIDmezeAVPD6I63hEwWnQAQNVXf7CRB2L+qy3GEkKVDV0jc= =WPBZ -----END PGP SIGNATURE----- --sl34vmva77hxhbwl-- From owner-freebsd-arch@freebsd.org Thu Apr 20 22:18:59 2017 Return-Path: Delivered-To: freebsd-arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A7DF7D48F56 for ; Thu, 20 Apr 2017 22:18:59 +0000 (UTC) (envelope-from mat@FreeBSD.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 87D90252 for ; Thu, 20 Apr 2017 22:18:59 +0000 (UTC) (envelope-from mat@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id 8191AD48F54; Thu, 20 Apr 2017 22:18:59 +0000 (UTC) Delivered-To: arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8115AD48F52; Thu, 20 Apr 2017 22:18:59 +0000 (UTC) (envelope-from mat@FreeBSD.org) Received: from prod2.absolight.net (prod2.absolight.net [79.143.243.136]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "plouf.absolight.net", Issuer "CAcert Class 3 Root" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 42166250; Thu, 20 Apr 2017 22:18:58 +0000 (UTC) (envelope-from mat@FreeBSD.org) Received: from prod2.absolight.net (localhost [127.0.0.1]) by prod2.absolight.net (Postfix) with ESMTP id 2B0BDBDC89; Fri, 21 Apr 2017 00:18:56 +0200 (CEST) Received: from atuin.in.mat.cc (atuin.in.mat.cc [79.143.241.205]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by prod2.absolight.net (Postfix) with ESMTPSA id 7E37BBDC85; Fri, 21 Apr 2017 00:18:55 +0200 (CEST) Subject: Re: manpath change for ports ? To: Baptiste Daroussin Cc: ports@FreeBSD.org, Koop Mast , portmgr@FreeBSD.org, arch@FreeBSD.org References: <20170306235610.cmpxk27jhoafel6l@ivaldir.net> <1492723094.55896.22.camel@FreeBSD.org> <20170420212153.cawvn4xsxuwuebfu@ivaldir.net> <20170420221631.yxukhuwo4tn7blte@ivaldir.net> From: Mathieu Arnold Organization: Absolight / The FreeBSD Foundation Message-ID: Date: Fri, 21 Apr 2017 00:18:53 +0200 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:52.0) Gecko/20100101 Thunderbird/52.0.1 MIME-Version: 1.0 In-Reply-To: <20170420221631.yxukhuwo4tn7blte@ivaldir.net> Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="NSPFsim5tGUQ4qiAXaBueWBP9ltCk5QLS" X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Apr 2017 22:18:59 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --NSPFsim5tGUQ4qiAXaBueWBP9ltCk5QLS Content-Type: multipart/mixed; boundary="SvU7srde9mTECapXNjHKcOugCkKahIbr3"; protected-headers="v1" From: Mathieu Arnold To: Baptiste Daroussin Cc: ports@FreeBSD.org, Koop Mast , portmgr@FreeBSD.org, arch@FreeBSD.org Message-ID: Subject: Re: manpath change for ports ? References: <20170306235610.cmpxk27jhoafel6l@ivaldir.net> <1492723094.55896.22.camel@FreeBSD.org> <20170420212153.cawvn4xsxuwuebfu@ivaldir.net> <20170420221631.yxukhuwo4tn7blte@ivaldir.net> In-Reply-To: <20170420221631.yxukhuwo4tn7blte@ivaldir.net> --SvU7srde9mTECapXNjHKcOugCkKahIbr3 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Content-Language: fr Le 21/04/2017 =C3=A0 00:16, Baptiste Daroussin a =C3=A9crit : > On Fri, Apr 21, 2017 at 12:13:52AM +0200, Mathieu Arnold wrote: >> Le 20/04/2017 =C3=A0 23:21, Baptiste Daroussin a =C3=A9crit : >>> On Thu, Apr 20, 2017 at 11:18:14PM +0200, Koop Mast wrote: >>>> On Tue, 2017-03-07 at 00:56 +0100, Baptiste Daroussin wrote: >>>>> Hi all, >>>>> >>>>> I would like to propose a change in the localbase hier for ports >>>>> >>>>> I think we should add /usr/local/share/man in the manpath along wit= h >>>>> at first >>>>> and maybe instead of in long term. >>>>> >>>>> The reason is: >>>>> - /usr/local/share/man seems more consistent to me with base which >>>>> have: >>>>> /usr/share/man >>>>> - It will remove lots of patches from the ports tree where were we >>>>> need to patch >>>>> upstream build system to install in a non usual path. >>>>> >>>>> My proposal is to add to the manpath /usr/local/share/man in defaul= t >>>>> man(1) >>>>> command in FreeBSD 12 (MFCed to 11-STABLE) >>>>> >>>>> and either provide an errata for 11.0/10.3 or a >>>>> /usr/local/etc/man.d/something.conf via a port or something like th= at >>>>> for those >>>>> two, what do you think? >>>>> >>>>> For the same reason I would like to allow porters to stop patching >>>>> (with pathfix >>>>> or anything else) the path for pkgconfig files and allow >>>>> /usr/local/lib/pkgconfig along with the current >>>>> /usr/local/libdata/pkgconfig:/usr/libdata/pkgconfig >>>>> >>>>> Which will also remove tons of hacks from the ports tree. >>>>> >>>>> What do you think? >>>>> >>>>> Best regards, >>>>> Bapt >>>> Hello, >>>> >>>> I recently committed the USES for the meson build system to ports. T= his >>>> USES configures the meson build system with some default variables >>>> which includes the location of the man pages. This setting is just a= >>>> flag to the meson command so it easy to change. >>>> >>>> Meson also handles the generation and installation of pkg-config fil= es >>>> that a port wants. The problem is that this is handled by the script= >>>> itself and there is no way to configure it, so we need to hack the >>>> meson port to change it from lib/pkg-config to libdata/pkg-config li= ke >>>> we currently are using. (1) Or add a hack to meson.mk to move the pk= g- >>>> config to the right location (evil++ imho). >>>> >>>> My point I want to make is that currently there is only 1 port build= >>>> via the meson system (graphics/graphene). Should we change man/pkg- >>>> config file locations now, it very easy. If we want to change them >>>> later we will need to mass bump every meson build port. It is import= ant >>>> to note that GStreamer and GNOME are moving over to using meson inst= ead >>>> of autotools and that Wayland, Xorg en Mesa are exploring want is >>>> needed to make the switch. So I think it important that the decision= >>>> what to do is done now and that we stick with it. >>>> >>>> Reading the rest of the thread it seems nobody is really against the= >>>> proposed change of man and pkg-config path's. So how does one submit= a >>>> policy change like this? I'm also not sure I'm the right person to p= ush >>>> this, I just got back from a break and I don't want to really deal w= ith >>>> something super high profile right away. >>>> >>>> -Koop >>>> >>>> (1) I would like to see lib/pkg-config back in the search path of >>>> pkgconf since that means I don't have to do a crash course python >>>> programming. >>> Would be nice is portmgr can step on this, let's reduce this discussi= on for now >>> on pkgconf. >> >> I am waiting on an exp-run to fix this once and for all. >> >> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D218067 >> >> When that is committed, anything can be added to the path pkgconfig >> searches, ports will always install it in the right place. >> > Sorry but why? why not moving libdata/pkgconfig to lib/pkgconfig? what = is the > rationale? Because a lot of build software know that on FreeBSD, the .pc file go in libdata/pkgconfig. If we move to some other place, we'll have a USES=3Dpathfixmore for the next 25 years until everyone understands we moved it some place else. --=20 Mathieu Arnold --SvU7srde9mTECapXNjHKcOugCkKahIbr3-- --NSPFsim5tGUQ4qiAXaBueWBP9ltCk5QLS Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQJ8BAEBCgBmBQJY+TPOXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzQUI2OTc4OUQyRUQxMjEwNjQ0MEJBNUIz QTQ1MTZGMzUxODNDRTQ4AAoJEDpFFvNRg85Ih3IP/jCByDscosFbSndXLSSwpNPQ BtxU7CmNDE/RqufUDg47G5t0UgNGmbIu8sjFHY2v9jk1PVt9s6rhdnqWEoF2EzsL 36Jmbn2IyrbFMCd7Q+DT8vHXYN4Ahat8WjP9yw3Z5KMC1Z4L03wf7k9tmsFZB8DF Kmq5bjqoPBVED2hXlzlFD/rcpQzkWQE383LTIUWnA1E2mxlFQs6WKKFnSxpCRe8S 9DfZpfF9ltJhR1F7bK9V/VBc7QKyjZ2FErxb5YS3pxgV9diAVo96nRaxkPgNTDFU 3r+dx6vs4UDqiyP83p9IjTnD5r4ZBClrLKc+vz8LuNkjb3E7OYUaRpUbY3OFXWWN bb2DPWqsm+4o/OVD3VBLg1iPy17S0FdiltPVE9jKhZfTPpwGtGRrnuL02KM6tRx+ sEOeZrVK6kP4AiSDoeNIYCPX1JQ6HyFiaj4rj3iMTKan3qAgEPuNx6+eqwoW0n0C +g3HL96ZkfZvoQXF+VdvLTWP3s8FDcB3wn4OsWWcEfRCK/CShBrCVrnO+pKnVmfa MPFUFIzsrUD9TW4CcK3wONaaFGdi7YwAG/8vqQgMAy7N6JICGFKhGtQ2noRyg0to s90ZJ5CTMNfY82iPXEzd3AabIWcSl9hOb6WdVCqMmerXHozxIkm0jCglxM/RuWiW H0nX1DoOOFK/g3fXhU96 =90tQ -----END PGP SIGNATURE----- --NSPFsim5tGUQ4qiAXaBueWBP9ltCk5QLS-- From owner-freebsd-arch@freebsd.org Thu Apr 20 22:21:56 2017 Return-Path: Delivered-To: freebsd-arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 67DDAD4828E for ; Thu, 20 Apr 2017 22:21:56 +0000 (UTC) (envelope-from bapt@FreeBSD.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 5299597F for ; Thu, 20 Apr 2017 22:21:56 +0000 (UTC) (envelope-from bapt@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id 4EFDDD4828B; Thu, 20 Apr 2017 22:21:56 +0000 (UTC) Delivered-To: arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4E885D48289; Thu, 20 Apr 2017 22:21:56 +0000 (UTC) (envelope-from bapt@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [96.47.72.132]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2BBEA97C; Thu, 20 Apr 2017 22:21:56 +0000 (UTC) (envelope-from bapt@FreeBSD.org) Received: by freefall.freebsd.org (Postfix, from userid 1235) id 9E3EE57B7; Thu, 20 Apr 2017 22:21:54 +0000 (UTC) Date: Fri, 21 Apr 2017 00:21:54 +0200 From: Baptiste Daroussin To: Mathieu Arnold Cc: ports@FreeBSD.org, Koop Mast , arch@FreeBSD.org, portmgr@FreeBSD.org Subject: Re: manpath change for ports ? Message-ID: <20170420222154.wtk5zvprn2g5b6ny@ivaldir.net> References: <20170306235610.cmpxk27jhoafel6l@ivaldir.net> <1492723094.55896.22.camel@FreeBSD.org> <20170420212153.cawvn4xsxuwuebfu@ivaldir.net> <20170420221631.yxukhuwo4tn7blte@ivaldir.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="jbc5mn23tydn6e5r" Content-Disposition: inline In-Reply-To: User-Agent: NeoMutt/20170306 (1.8.0) X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Apr 2017 22:21:56 -0000 --jbc5mn23tydn6e5r Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Apr 21, 2017 at 12:18:53AM +0200, Mathieu Arnold wrote: > Le 21/04/2017 =E0 00:16, Baptiste Daroussin a =E9crit : > > On Fri, Apr 21, 2017 at 12:13:52AM +0200, Mathieu Arnold wrote: > >> Le 20/04/2017 =E0 23:21, Baptiste Daroussin a =E9crit : > >>> On Thu, Apr 20, 2017 at 11:18:14PM +0200, Koop Mast wrote: > >>>> On Tue, 2017-03-07 at 00:56 +0100, Baptiste Daroussin wrote: > >>>>> Hi all, > >>>>> > >>>>> I would like to propose a change in the localbase hier for ports > >>>>> > >>>>> I think we should add /usr/local/share/man in the manpath along with > >>>>> at first > >>>>> and maybe instead of in long term. > >>>>> > >>>>> The reason is: > >>>>> - /usr/local/share/man seems more consistent to me with base which > >>>>> have: > >>>>> /usr/share/man > >>>>> - It will remove lots of patches from the ports tree where were we > >>>>> need to patch > >>>>> upstream build system to install in a non usual path. > >>>>> > >>>>> My proposal is to add to the manpath /usr/local/share/man in default > >>>>> man(1) > >>>>> command in FreeBSD 12 (MFCed to 11-STABLE) > >>>>> > >>>>> and either provide an errata for 11.0/10.3 or a > >>>>> /usr/local/etc/man.d/something.conf via a port or something like th= at > >>>>> for those > >>>>> two, what do you think? > >>>>> > >>>>> For the same reason I would like to allow porters to stop patching > >>>>> (with pathfix > >>>>> or anything else) the path for pkgconfig files and allow > >>>>> /usr/local/lib/pkgconfig along with the current > >>>>> /usr/local/libdata/pkgconfig:/usr/libdata/pkgconfig > >>>>> > >>>>> Which will also remove tons of hacks from the ports tree. > >>>>> > >>>>> What do you think? > >>>>> > >>>>> Best regards, > >>>>> Bapt > >>>> Hello, > >>>> > >>>> I recently committed the USES for the meson build system to ports. T= his > >>>> USES configures the meson build system with some default variables > >>>> which includes the location of the man pages. This setting is just a > >>>> flag to the meson command so it easy to change. > >>>> > >>>> Meson also handles the generation and installation of pkg-config fil= es > >>>> that a port wants. The problem is that this is handled by the script > >>>> itself and there is no way to configure it, so we need to hack the > >>>> meson port to change it from lib/pkg-config to libdata/pkg-config li= ke > >>>> we currently are using. (1) Or add a hack to meson.mk to move the pk= g- > >>>> config to the right location (evil++ imho). > >>>> > >>>> My point I want to make is that currently there is only 1 port build > >>>> via the meson system (graphics/graphene). Should we change man/pkg- > >>>> config file locations now, it very easy. If we want to change them > >>>> later we will need to mass bump every meson build port. It is import= ant > >>>> to note that GStreamer and GNOME are moving over to using meson inst= ead > >>>> of autotools and that Wayland, Xorg en Mesa are exploring want is > >>>> needed to make the switch. So I think it important that the decision > >>>> what to do is done now and that we stick with it. > >>>> > >>>> Reading the rest of the thread it seems nobody is really against the > >>>> proposed change of man and pkg-config path's. So how does one submit= a > >>>> policy change like this? I'm also not sure I'm the right person to p= ush > >>>> this, I just got back from a break and I don't want to really deal w= ith > >>>> something super high profile right away. > >>>> > >>>> -Koop > >>>> > >>>> (1) I would like to see lib/pkg-config back in the search path of > >>>> pkgconf since that means I don't have to do a crash course python > >>>> programming. > >>> Would be nice is portmgr can step on this, let's reduce this discussi= on for now > >>> on pkgconf. > >> > >> I am waiting on an exp-run to fix this once and for all. > >> > >> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D218067 > >> > >> When that is committed, anything can be added to the path pkgconfig > >> searches, ports will always install it in the right place. > >> > > Sorry but why? why not moving libdata/pkgconfig to lib/pkgconfig? what = is the > > rationale? > Because a lot of build software know that on FreeBSD, the .pc file go in > libdata/pkgconfig. If we move to some other place, we'll have a > USES=3Dpathfixmore for the next 25 years until everyone understands we > moved it some place else. >=20 ok a point for you there :) Bapt --jbc5mn23tydn6e5r Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEgOTj3suS2urGXVU3Y4mL3PG3PloFAlj5NIIACgkQY4mL3PG3 PloiJw/9GYDGgxSamCyELEIfl+BkKlI2qqOBAo3xUkidXNPEVmmsIM/pbEc1oXzF 0ZArbRQSpkLHVaJwIxIF7ITfPtcDexgfbLBNDHFcp+VNahVdL6Zja+0ut1gwUboK zwszn3EbyKoKFh+dz1yG0Gcf3obCmTyqXlA4Oh/SYEaUT3jWZhkp1CRDB1E9Mu1D KnNxxQ2mf85wknxBwPVxIiRf8benyciB87dYPXkVNZru7LpFfLvUpP8f96cKEteb 6WT9G1gPnlR4zfDDjdkul9JUEQ5Dsk2PtMv6ILpwS7lPrR5/3mDXIMAhRn9H/feW jKOL8XGpaPN7jzSlDFw695b0qWtS64qW1oV8WrNzG7RuxkiJxuNCRIs7YcPP/diJ JbdxPiu9AgAGgRHJ8DQPAOMe3K6v2Ze5xWg3R1EQHfS7+Ra9XJvhZG42aeXzcBn4 I/ePIdyPTvfEsv/ECLgTjekz/O8S4at4rm/oHI2VX8oIfEYCroblkAl6uAldoWxL LI3AhhvBbvvgslrtw1n6TN3HdsjVzWPrkOmCuqN0uiALiLG5t3jOe7fcG1IfP2QS 3GJ0NcoxN/GS3DfJRk2A+f0DPadhHFuebZQSR9wRqr+s0Kbcew1GXOA5z2RHO1u9 VAg4jd0CCNDq/lUSvOz+UfaHrot58IYxddtz36+yPhDg4f+7pD0= =6sBy -----END PGP SIGNATURE----- --jbc5mn23tydn6e5r-- From owner-freebsd-arch@freebsd.org Thu Apr 20 22:29:20 2017 Return-Path: Delivered-To: freebsd-arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B33A1D483D3 for ; Thu, 20 Apr 2017 22:29:20 +0000 (UTC) (envelope-from mat@FreeBSD.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 91953BBA for ; Thu, 20 Apr 2017 22:29:20 +0000 (UTC) (envelope-from mat@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id 8DCA8D483D1; Thu, 20 Apr 2017 22:29:20 +0000 (UTC) Delivered-To: arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8B9ABD483D0; Thu, 20 Apr 2017 22:29:20 +0000 (UTC) (envelope-from mat@FreeBSD.org) Received: from prod2.absolight.net (mx3.absolight.net [IPv6:2a01:678:2:100::25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "plouf.absolight.net", Issuer "CAcert Class 3 Root" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 3993CBB9; Thu, 20 Apr 2017 22:29:20 +0000 (UTC) (envelope-from mat@FreeBSD.org) Received: from prod2.absolight.net (localhost [127.0.0.1]) by prod2.absolight.net (Postfix) with ESMTP id 23E94BDC89; Fri, 21 Apr 2017 00:29:18 +0200 (CEST) Received: from atuin.in.mat.cc (atuin.in.mat.cc [79.143.241.205]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by prod2.absolight.net (Postfix) with ESMTPSA id B3CB7BDC85; Fri, 21 Apr 2017 00:29:17 +0200 (CEST) Subject: Re: manpath change for ports ? To: Baptiste Daroussin Cc: ports@FreeBSD.org, Koop Mast , arch@FreeBSD.org, portmgr@FreeBSD.org References: <20170306235610.cmpxk27jhoafel6l@ivaldir.net> <1492723094.55896.22.camel@FreeBSD.org> <20170420212153.cawvn4xsxuwuebfu@ivaldir.net> <20170420221631.yxukhuwo4tn7blte@ivaldir.net> <20170420222154.wtk5zvprn2g5b6ny@ivaldir.net> From: Mathieu Arnold Organization: Absolight / The FreeBSD Foundation Message-ID: Date: Fri, 21 Apr 2017 00:29:15 +0200 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:52.0) Gecko/20100101 Thunderbird/52.0.1 MIME-Version: 1.0 In-Reply-To: <20170420222154.wtk5zvprn2g5b6ny@ivaldir.net> Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="M6ruqCFds9cMr1iEvV2uVecaNHTDUjGxn" X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Apr 2017 22:29:20 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --M6ruqCFds9cMr1iEvV2uVecaNHTDUjGxn Content-Type: multipart/mixed; boundary="u6useOiVKf44ivSEJpPrGEuWSVXgnjswi"; protected-headers="v1" From: Mathieu Arnold To: Baptiste Daroussin Cc: ports@FreeBSD.org, Koop Mast , arch@FreeBSD.org, portmgr@FreeBSD.org Message-ID: Subject: Re: manpath change for ports ? References: <20170306235610.cmpxk27jhoafel6l@ivaldir.net> <1492723094.55896.22.camel@FreeBSD.org> <20170420212153.cawvn4xsxuwuebfu@ivaldir.net> <20170420221631.yxukhuwo4tn7blte@ivaldir.net> <20170420222154.wtk5zvprn2g5b6ny@ivaldir.net> In-Reply-To: <20170420222154.wtk5zvprn2g5b6ny@ivaldir.net> --u6useOiVKf44ivSEJpPrGEuWSVXgnjswi Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Content-Language: en-US Le 21/04/2017 =C3=A0 00:21, Baptiste Daroussin a =C3=A9crit : > On Fri, Apr 21, 2017 at 12:18:53AM +0200, Mathieu Arnold wrote: >> Le 21/04/2017 =C3=A0 00:16, Baptiste Daroussin a =C3=A9crit : >>> On Fri, Apr 21, 2017 at 12:13:52AM +0200, Mathieu Arnold wrote: >>>> Le 20/04/2017 =C3=A0 23:21, Baptiste Daroussin a =C3=A9crit : >>>>> On Thu, Apr 20, 2017 at 11:18:14PM +0200, Koop Mast wrote: >>>>>> On Tue, 2017-03-07 at 00:56 +0100, Baptiste Daroussin wrote: >>>>>>> Hi all, >>>>>>> >>>>>>> I would like to propose a change in the localbase hier for ports >>>>>>> >>>>>>> I think we should add /usr/local/share/man in the manpath along w= ith >>>>>>> at first >>>>>>> and maybe instead of in long term. >>>>>>> >>>>>>> The reason is: >>>>>>> - /usr/local/share/man seems more consistent to me with base whic= h >>>>>>> have: >>>>>>> /usr/share/man >>>>>>> - It will remove lots of patches from the ports tree where were w= e >>>>>>> need to patch >>>>>>> upstream build system to install in a non usual path. >>>>>>> >>>>>>> My proposal is to add to the manpath /usr/local/share/man in defa= ult >>>>>>> man(1) >>>>>>> command in FreeBSD 12 (MFCed to 11-STABLE) >>>>>>> >>>>>>> and either provide an errata for 11.0/10.3 or a >>>>>>> /usr/local/etc/man.d/something.conf via a port or something like = that >>>>>>> for those >>>>>>> two, what do you think? >>>>>>> >>>>>>> For the same reason I would like to allow porters to stop patchin= g >>>>>>> (with pathfix >>>>>>> or anything else) the path for pkgconfig files and allow >>>>>>> /usr/local/lib/pkgconfig along with the current >>>>>>> /usr/local/libdata/pkgconfig:/usr/libdata/pkgconfig >>>>>>> >>>>>>> Which will also remove tons of hacks from the ports tree. >>>>>>> >>>>>>> What do you think? >>>>>>> >>>>>>> Best regards, >>>>>>> Bapt >>>>>> Hello, >>>>>> >>>>>> I recently committed the USES for the meson build system to ports.= This >>>>>> USES configures the meson build system with some default variables= >>>>>> which includes the location of the man pages. This setting is just= a >>>>>> flag to the meson command so it easy to change. >>>>>> >>>>>> Meson also handles the generation and installation of pkg-config f= iles >>>>>> that a port wants. The problem is that this is handled by the scri= pt >>>>>> itself and there is no way to configure it, so we need to hack the= >>>>>> meson port to change it from lib/pkg-config to libdata/pkg-config = like >>>>>> we currently are using. (1) Or add a hack to meson.mk to move the = pkg- >>>>>> config to the right location (evil++ imho). >>>>>> >>>>>> My point I want to make is that currently there is only 1 port bui= ld >>>>>> via the meson system (graphics/graphene). Should we change man/pkg= - >>>>>> config file locations now, it very easy. If we want to change them= >>>>>> later we will need to mass bump every meson build port. It is impo= rtant >>>>>> to note that GStreamer and GNOME are moving over to using meson in= stead >>>>>> of autotools and that Wayland, Xorg en Mesa are exploring want is >>>>>> needed to make the switch. So I think it important that the decisi= on >>>>>> what to do is done now and that we stick with it. >>>>>> >>>>>> Reading the rest of the thread it seems nobody is really against t= he >>>>>> proposed change of man and pkg-config path's. So how does one subm= it a >>>>>> policy change like this? I'm also not sure I'm the right person to= push >>>>>> this, I just got back from a break and I don't want to really deal= with >>>>>> something super high profile right away. >>>>>> >>>>>> -Koop >>>>>> >>>>>> (1) I would like to see lib/pkg-config back in the search path of >>>>>> pkgconf since that means I don't have to do a crash course python >>>>>> programming. >>>>> Would be nice is portmgr can step on this, let's reduce this discus= sion for now >>>>> on pkgconf. >>>> I am waiting on an exp-run to fix this once and for all. >>>> >>>> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D218067 >>>> >>>> When that is committed, anything can be added to the path pkgconfig >>>> searches, ports will always install it in the right place. >>>> >>> Sorry but why? why not moving libdata/pkgconfig to lib/pkgconfig? wha= t is the >>> rationale? >> Because a lot of build software know that on FreeBSD, the .pc file go = in >> libdata/pkgconfig. If we move to some other place, we'll have a >> USES=3Dpathfixmore for the next 25 years until everyone understands we= >> moved it some place else. >> > ok a point for you there :) I have no problems having lib/pkgconfig added to the search path so that people who build stuff manually have their .pc files in a place where pkg-config can read them, but I really do not want the ports to install them in more than one place. My PR solves that problem, all the ports will forcibly end up in libdata/pkgconfig, we could even drop USES=3Dpathfix. --=20 Mathieu Arnold --u6useOiVKf44ivSEJpPrGEuWSVXgnjswi-- --M6ruqCFds9cMr1iEvV2uVecaNHTDUjGxn Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQJ8BAEBCgBmBQJY+TY8XxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzQUI2OTc4OUQyRUQxMjEwNjQ0MEJBNUIz QTQ1MTZGMzUxODNDRTQ4AAoJEDpFFvNRg85I2ukP/iewLpTKlpzI/O9A6eNDmfJv QsOH7t3iK9tc/UcnP45RxCi4ZMqTD4xY4wnKnSnlrQDoprxnVxkpU3cmGAX3RgWa VH2sbsNIKh1TmDoZNv4Bk6qDNd+g/gHYcd74s7UuMIh+iXX0R4vF/nI7Mket+inl UvAxmiLk6rez/a7RQG36wzmds4ftMoJtd09MMY2utP7DQEj6yycI/N7osgdXCo4r /cS+sELUBHlLY0eR5Alje9SBSfA66HzMojW04Z0uiQb5xhJyqKzHr14vz7Ucqfqd bld7iHwy2O/FGjoISANoVoWPJKyzDMW/AJdWI07tcHhnEk4TgsYxaf4XyHbvkfuI hSqkZ5XGHcY9djW+qmE2TQr7c5iVPMu16GxqRZNrVhmRWGayaQGXFvdiIGNHAGer F+kcZuAP8j8rJeqoSoTs0g7xk+HtORVSkLaZNtRQNjMP/FoxnSaaqwSF+Jpy1mj/ HRmH3TxPXhp0vnfmMFu/Wby6AmNfjEPRGOpPjZYgV6F9Or5YhhAFUfHCVjTRFr55 j3Vvdn9GBlsNAfDGl8o7R1COkpyaw4m4caBAsFfAs3k4Vp0GewDW7yPh/tnKAopJ CRWXuiZTb+8EnMO4xX7RwMqNECXekf/s351pyF46e0JfkVa2g8A5pUjs9m0Mjx3e Forxsjpu98vCEzcowu8m =twSm -----END PGP SIGNATURE----- --M6ruqCFds9cMr1iEvV2uVecaNHTDUjGxn-- From owner-freebsd-arch@freebsd.org Fri Apr 21 14:07:09 2017 Return-Path: Delivered-To: freebsd-arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B2C07D41BC5 for ; Fri, 21 Apr 2017 14:07:09 +0000 (UTC) (envelope-from tijl@freebsd.org) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 873ADF6A for ; Fri, 21 Apr 2017 14:07:09 +0000 (UTC) (envelope-from tijl@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 8404AD41BC3; Fri, 21 Apr 2017 14:07:09 +0000 (UTC) Delivered-To: arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 81DCED41BC2; Fri, 21 Apr 2017 14:07:09 +0000 (UTC) (envelope-from tijl@freebsd.org) Received: from mailrelay117.isp.belgacom.be (mailrelay117.isp.belgacom.be [195.238.20.144]) (using TLSv1.2 with cipher RC4-SHA (128/128 bits)) (Client CN "relay.skynet.be", Issuer "GlobalSign Organization Validation CA - SHA256 - G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1B410F69; Fri, 21 Apr 2017 14:07:07 +0000 (UTC) (envelope-from tijl@freebsd.org) X-Belgacom-Dynamic: yes IronPort-PHdr: =?us-ascii?q?9a23=3AmvGcoxbLF+sz1V4j1bUCVhH/LSx+4OfEezUN459i?= =?us-ascii?q?sYplN5qZpsy+ZR7h7PlgxGXEQZ/co6odzbGH7+a4ASQp2tWoiDg6aptCVhsI24?= =?us-ascii?q?09vjcLJ4q7M3D9N+PgdCcgHc5PBxdP9nC/NlVJSo6lPwWB6nK94iQPFRrhKAF7?= =?us-ascii?q?Ovr6GpLIj8Swyuu+54Dfbx9GiTe5br5+Ngm6oRnMvcQKnIVuLbo8xAHUqXVSYe?= =?us-ascii?q?RWwm1oJVOXnxni48q74YBu/SdNtf8/7sBMSar1cbg2QrxeFzQmLns65Nb3uhnZ?= =?us-ascii?q?TAuA/WUTX2MLmRdVGQfF7RX6XpDssivms+d2xSeXMdHqQb0yRD+v9LlgRgP2hy?= =?us-ascii?q?gbNj456GDXhdJ2jKJHuxKquhhzz5fJbI2JKPZye6XQds4YS2VcRMZcTyJPDIOi?= =?us-ascii?q?YYUSDOQOP+hYoIbhqFUBtha+GRCsCP/zxjNUmnP736s32PkhHwHc2wwgGsoDvm?= =?us-ascii?q?rVrNX3MKcZTP64zK7PzTXYcfxW3C3y6I7Tchs8pvyMQbNwccjVyUQ0Fw3FlEuf?= =?us-ascii?q?ppL4Mj2I2OoBqW+b7/BvVe+2jWMstg9/oj+qxsg2i4nJgJoYyl7e9Spn3ok6Ps?= =?us-ascii?q?a4R1Nhbd6jCptQuCeXPJZ1TMM6W2xluyQ3xqcHtJO7ZiQG1ZAqyhDFZ/CZboSF?= =?us-ascii?q?4RTuX/uLLzhinnJqYre/ig638Uin1+LzSNG50E1PripZitnMsW0N1wDL5siHVP?= =?us-ascii?q?R9+kCh1C6M1w/J7uFEIEU0mrTBK54m2LIwipsTsUbHHiPshEr2i6iWdl469eit?= =?us-ascii?q?8evnZK7mqoWbN49uhQHyKqUumsqhDuQkKgUDXGqW9f692bDj50H1XbFHg/Msnq?= =?us-ascii?q?XHrZzXJtwXpqujDA9U1oYj5Qy/DzCj0NkAgXkHLVBFeBacgojnIVHBPu73Auyk?= =?us-ascii?q?g1uxijtrwOrGPrL5DpXXMnfDiKvhfap660NE0Aozyspf545RCrEOOvL+QUHxtM?= =?us-ascii?q?bGARAnKAO02PvoBM961oMEVmKFGrWZP7/KsV+U+uIvJPGBa5UPuDnhK/go/PDu?= =?us-ascii?q?jWUnllADZqapxoYYZGq/HvR8LEWTeWDsjcsZEWcWogo+S/TniF6MUD5WfHuyUb?= =?us-ascii?q?g86S8lB429FofMW5qhgLub3Ce0BpdWfHxJCkiQEXf0cIWJQ+8MaCWIIs99iTwJ?= =?us-ascii?q?TrahS5U/2h6wrwD60KdoIvDT+i0CupLpzMJ16PHLlREu6Tx0CNyQ3HqXQGFsgm?= =?us-ascii?q?MFXDE23LphrkNj0ViDyrV3j+ZfFdxJ6PNDSh06OoLEz+xmF9DyXRrMftKTR1a6?= =?us-ascii?q?WdimDysxQcwvzNAVeEZyBs+ujhfZ3yqlUPcpkOmuDYA086/Bl1HrIcF5xz6S0a?= =?us-ascii?q?A9p3c8T8ZlDkHggbRwoVv9HYnMxnmYlaLiXqMbxyPI/WGYhT6SvUNceCBqXKjv?= =?us-ascii?q?ZlxZYVHZ+4eqrnjeRqOjXOx0ejBKztSPf+4TMoXk?= X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: =?us-ascii?q?A2DdEAA7EfpY/9rBQVdcHAEBBAEBCgEBF?= =?us-ascii?q?wEBBAEBCgEBgylREHoSg2eLCI8UgWIqAUWXAyyCQoM2AoQJRBQBAQEBAQEBAQE?= =?us-ascii?q?BAWoogjMiAYJAAQUjMyMQCw4KAgIFIQICDyoeBhOKIAqpSoImiyEBAQEBAQEEA?= =?us-ascii?q?QEBAQEBHQWBC4clgmU0gxiERYJfBZ1BhxeLYneQbZQZNiGBBkMtCIcuPjUBiTU?= =?us-ascii?q?BAQE?= X-IPAS-Result: =?us-ascii?q?A2DdEAA7EfpY/9rBQVdcHAEBBAEBCgEBFwEBBAEBCgEBgyl?= =?us-ascii?q?REHoSg2eLCI8UgWIqAUWXAyyCQoM2AoQJRBQBAQEBAQEBAQEBAWoogjMiAYJAA?= =?us-ascii?q?QUjMyMQCw4KAgIFIQICDyoeBhOKIAqpSoImiyEBAQEBAQEEAQEBAQEBHQWBC4c?= =?us-ascii?q?lgmU0gxiERYJfBZ1BhxeLYneQbZQZNiGBBkMtCIcuPjUBiTUBAQE?= Received: from 218.193-65-87.adsl-dyn.isp.belgacom.be (HELO kalimero.tijl.coosemans.org) ([87.65.193.218]) by relay.skynet.be with ESMTP; 21 Apr 2017 16:05:49 +0200 Received: from kalimero.tijl.coosemans.org (kalimero.tijl.coosemans.org [127.0.0.1]) by kalimero.tijl.coosemans.org (8.15.2/8.15.2) with ESMTP id v3LE5mMT041795; Fri, 21 Apr 2017 16:05:48 +0200 (CEST) (envelope-from tijl@FreeBSD.org) Date: Fri, 21 Apr 2017 16:05:48 +0200 From: Tijl Coosemans To: Mathieu Arnold Cc: Baptiste Daroussin , ports@FreeBSD.org, Koop Mast , arch@FreeBSD.org, portmgr@FreeBSD.org Subject: Re: manpath change for ports ? Message-ID: <20170421160548.634ec1bb@kalimero.tijl.coosemans.org> In-Reply-To: References: <20170306235610.cmpxk27jhoafel6l@ivaldir.net> <1492723094.55896.22.camel@FreeBSD.org> <20170420212153.cawvn4xsxuwuebfu@ivaldir.net> <20170420221631.yxukhuwo4tn7blte@ivaldir.net> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Apr 2017 14:07:09 -0000 On Fri, 21 Apr 2017 00:18:53 +0200 Mathieu Arnold wrote: > Le 21/04/2017 =C3=A0 00:16, Baptiste Daroussin a =C3=A9crit: >> On Fri, Apr 21, 2017 at 12:13:52AM +0200, Mathieu Arnold wrote: >>> I am waiting on an exp-run to fix this once and for all. >>> >>> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D218067 >>> >>> When that is committed, anything can be added to the path pkgconfig >>> searches, ports will always install it in the right place. >> >> Sorry but why? why not moving libdata/pkgconfig to lib/pkgconfig? what >> is the rationale? > > Because a lot of build software know that on FreeBSD, the .pc file go > in libdata/pkgconfig. If we move to some other place, we'll have a > USES=3Dpathfixmore for the next 25 years until everyone understands we > moved it some place else. 1. It's not a lot. Certainly the amount of software that does not know about libdata is way bigger. 2. You don't need USES=3Dpathfixmore, you just change the fixup target in your patch to move files in the other direction. This fixup can then be removed in 25 years (less if you let it print a warning) while your fixup will have to be kept forever. 3. Proper porting of emulators/wine to amd64 requires building 32 bit versions of dependencies. Their pkgconfig files would go to lib32/pkgconfig when configured with --libdir=3D${PREFIX}/lib32 while something like libdata/pkgconfig32 would require yet more patches and fixups. Any difference from Linux makes porting work harder, so there should be good reasons and there are none whatsoever to use libdata/pkgconfig over lib/pkgconfig. I really don't get why portmgr keeps blocking this change every time it comes up in the past few years.