From nobody Thu Mar 14 22:24:27 2024 X-Original-To: ports@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Twhkl0dBNz5DjRT for ; Thu, 14 Mar 2024 22:24:31 +0000 (UTC) (envelope-from SRS0=fhg4=KU=quip.cz=000.fbsd@elsa.codelab.cz) Received: from elsa.codelab.cz (elsa.codelab.cz [94.124.105.4]) (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 4Twhkk0hs5z51Zd for ; Thu, 14 Mar 2024 22:24:29 +0000 (UTC) (envelope-from SRS0=fhg4=KU=quip.cz=000.fbsd@elsa.codelab.cz) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=quip.cz header.s=private header.b=AJ46ZHrc; dkim=pass header.d=quip.cz header.s=private header.b=I2zZ34Gj; dmarc=none; spf=none (mx1.freebsd.org: domain of "SRS0=fhg4=KU=quip.cz=000.fbsd@elsa.codelab.cz" has no SPF policy when checking 94.124.105.4) smtp.mailfrom="SRS0=fhg4=KU=quip.cz=000.fbsd@elsa.codelab.cz" Received: from elsa.codelab.cz (localhost [127.0.0.1]) by elsa.codelab.cz (Postfix) with ESMTP id 81BB2D78AA for ; Thu, 14 Mar 2024 23:24:28 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=quip.cz; s=private; t=1710455068; bh=UTrWvxwkspIobWKaT7oFG0GYSMb7psGxWRxK0RchhHM=; h=Date:Subject:To:References:From:In-Reply-To; b=AJ46ZHrcZIqnoDvTRyLSfyXQgjgeQo68tm2by503ZkwEVblF9fpLlmV9cVe1eOqGl yXURAOixraSfEkcw548le/l8+R/J//WnCdR9IYFvLvQzOdmYl8phtuDXRVsLyRgf/M QBc68l9t64wa5cjlQQUu5Yi/b2gMQhAUYeLz0wnM= Received: from [192.168.145.49] (ip-89-177-27-225.bb.vodafone.cz [89.177.27.225]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by elsa.codelab.cz (Postfix) with ESMTPSA id 6C757D7889 for ; Thu, 14 Mar 2024 23:24:27 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=quip.cz; s=private; t=1710455067; bh=UTrWvxwkspIobWKaT7oFG0GYSMb7psGxWRxK0RchhHM=; h=Date:Subject:To:References:From:In-Reply-To; b=I2zZ34Gj4Ip/RWYP4SZPwkLm6u9Y71XosknmgMcN+1HKj6++p99pUNpVXrmRIQwNZ llWmh0nWodADQwXqakuC6gJUld28P7/dOJ4rJ58Vr4SL0g+gj/TSEZhNUap8Jw2TJ8 oPHEhKclozqG5FU9dKPF/42m+Yq2WQFreM3gD+HY= Message-ID: Date: Thu, 14 Mar 2024 23:24:27 +0100 List-Id: Porting software to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-ports List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-ports@freebsd.org X-BeenThere: freebsd-ports@freebsd.org MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: how to see order of make targets steps in ports tree? Content-Language: en-US To: ports@freebsd.org References: <610f900f-658f-474d-885a-abbe709a00f7@quip.cz> From: Miroslav Lachman <000.fbsd@quip.cz> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spamd-Bar: - X-Spamd-Result: default: False [-1.98 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.99)[-0.991]; FORGED_SENDER(0.30)[000.fbsd@quip.cz,SRS0=fhg4=KU=quip.cz=000.fbsd@elsa.codelab.cz]; R_DKIM_ALLOW(-0.20)[quip.cz:s=private]; MIME_GOOD(-0.10)[text/plain]; XM_UA_NO_VERSION(0.01)[]; R_SPF_NA(0.00)[no SPF record]; ARC_NA(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; RCVD_VIA_SMTP_AUTH(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:42000, ipnet:94.124.104.0/21, country:CZ]; DMARC_NA(0.00)[quip.cz]; MLMMJ_DEST(0.00)[ports@freebsd.org]; RCVD_TLS_LAST(0.00)[]; FROM_NEQ_ENVFROM(0.00)[000.fbsd@quip.cz,SRS0=fhg4=KU=quip.cz=000.fbsd@elsa.codelab.cz]; FROM_HAS_DN(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; TO_MATCH_ENVRCPT_ALL(0.00)[]; TO_DN_NONE(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[ports@freebsd.org]; DKIM_TRACE(0.00)[quip.cz:+] X-Rspamd-Queue-Id: 4Twhkk0hs5z51Zd On 14/03/2024 22:03, Tatsuki Makino wrote: > Hello. > > Various answers have already been given, however, here is a command that can produce interesting values on this. > > make -C /usr/ports/ports-mgmt/pkg -V _TARGETS_STAGES > make -C /usr/ports/ports-mgmt/pkg -V _SANITY_SEQ -V _PKG_SEQ -V _FETCH_SEQ -V _EXTRACT_SEQ -V OMITTED_HEREAFTER:P > > The -d option of make also displays some rather interesting things. > > make -C /usr/ports/ports-mgmt/pkg -n -d g1 > > In addition, variables such as _USES_target can be used to add interesting behavior. > For example, in the patch phase, rewriting by replace_cmd may be performed in addition to normal patching. > It makes make makepatch not smart to use. > It can be stopped by defining the following targets. ...I think I wrote that somewhere before :) > > _USES_patch+= 501:stop-patch > stop-patch: .NOTMAIN .PHONY > false > > I just don't know if it helps :) Thank you. I find these commands useful. Really interesting output. And this line should explain the order of patch and fix-shebang _PATCH_REAL_SEQ = ${:Uask-license} ${:Upatch-message} ${:Upatch-depends} ${:Ufix-shebang} ${:Udo-patch} Thanks again. Kind regards Miroslav Lachman