Subject: Re: [alpine-aports] [PATCH 2/3] newapkbuild: remove default prepare()
To: alpine-aports@lists.alpinelinux.org
References: <1454365949-60951-1-git-send-email-muh.muhten@gmail.com>
 <1454365949-60951-2-git-send-email-muh.muhten@gmail.com>
 <20160202065025.fc1318a9f038027d2aa32d63@mauras.ch>
From: Muh Muhten <muh.muhten@gmail.com>
Message-ID: <56B089FB.9070305@gmail.com>
Date: Tue, 2 Feb 2016 05:50:35 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:38.0)
 Gecko/20100101 Thunderbird/38.5.1
Precedence: list
MIME-Version: 1.0
In-Reply-To: <20160202065025.fc1318a9f038027d2aa32d63@mauras.ch>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit

Nothing special. An added prepare() will function correctly and be run 
instead of default prepare.

To clear up some confusion: this patch is intended to apply in the 
context of %1521; default_prepare is *not* implemented yet, I just sent 
in the two patches together.

Only APKBUILDs with no prepare() definition should be affected; there is 
no change to the logic when abuild calls prepare, only the default 
function definition changes from silent no-op to the patching behavior 
newapkbuild generates.

Michael

On 2016-02-02 12:50 AM, Olivier Mauras wrote:
> Hello,
>
> How does that behave if one adds prepare() back in the APKBUILD? prepare() can be used for other things than just patches.
>
> Regards,
> Olivier
>


---
Unsubscribe:  alpine-aports+unsubscribe@lists.alpinelinux.org
Help:         alpine-aports+help@lists.alpinelinux.org
---