From owner-freebsd-ports@freebsd.org Sun Apr 26 19:37:20 2020 Return-Path: Delivered-To: freebsd-ports@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id B72282BA6A2 for ; Sun, 26 Apr 2020 19:37:20 +0000 (UTC) (envelope-from bofh@freebsd.org) Received: from mailman.nyi.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 499J8J47Z5z3NMY for ; Sun, 26 Apr 2020 19:37:20 +0000 (UTC) (envelope-from bofh@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id 8BE622BA69D; Sun, 26 Apr 2020 19:37:20 +0000 (UTC) Delivered-To: ports@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 8A7E02BA69C; Sun, 26 Apr 2020 19:37:20 +0000 (UTC) (envelope-from bofh@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 499J8J1DL5z3NMX; Sun, 26 Apr 2020 19:37:20 +0000 (UTC) (envelope-from bofh@freebsd.org) Received: from mx.bofh.network (mx.bofh.network [IPv6:2001:19f0:5001:2b77:5400:2ff:fe7b:aa2c]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mx.bofh.network", Issuer "Let's Encrypt Authority X3" (verified OK)) (Authenticated sender: bofh/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id C85F813C75; Sun, 26 Apr 2020 19:37:19 +0000 (UTC) (envelope-from bofh@freebsd.org) Received: from [IPv6:2402:54c0:ffff:ffff:3c3f:b695:df7f:e11d] ( [2402:54c0:ffff:ffff:3c3f:b695:df7f:e11d]) by mx.bofh.network (OpenSMTPD) with ESMTPSA id b0d6a6f7 (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256:NO); Sun, 26 Apr 2020 19:37:13 +0000 (UTC) From: Muhammad Moinur Rahman Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\)) Subject: Using pkg in documentation Message-Id: <51F445F4-9F4F-4B64-BFC3-FBCC337A8267@freebsd.org> Date: Mon, 27 Apr 2020 01:37:09 +0600 Cc: python@freebsd.org To: "ports@freebsd.org" X-Mailer: Apple Mail (2.3608.80.23.2.2) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 26 Apr 2020 19:37:20 -0000 What is the way of mentioning about installing a py-package in = documentation? Let=E2=80=99s say now the default version of python is = 3.7 so in most of the cases we can write in our documentation that do = the following: # pkg install py37-babel But when the default version of python is changed this is no longer = going to work if it doesn=E2=80=99t have all flavors. Then there are = cases when we mention about porting and installation howto on upstream = and we need to update this regularly with every change of = DEFAULT_VERSIONS in python. So is there any way to pass PYTHON_DEFAULT with pkg install? One option = that I have thought about is pkg install -g py3\*-babel; but again once = when python 4 (forgive my brevity 3:)) is going to release this changes. = And I believe this is the same case for php too. Thanks in advance. Kind Regards, Moin=