From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mout.kundenserver.de ([212.227.126.187]) by metis.ext.pengutronix.de with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.84_2) (envelope-from ) id 1dVhPP-0003aS-TZ for ptxdist@pengutronix.de; Thu, 13 Jul 2017 18:56:12 +0200 Received: from idefix.home.lespocky.de ([79.205.193.116]) by mrelayeu.kundenserver.de (mreue002 [212.227.15.167]) with ESMTPSA (Nemesis) id 0LbUhX-1dxJBV0K1T-00lHHA for ; Thu, 13 Jul 2017 18:56:06 +0200 Received: from falbala.home.lespocky.de ([192.168.243.94]) by idefix.home.lespocky.de with esmtpsa (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.82) (envelope-from ) id 1dVhP4-0007Y6-K1 for ptxdist@pengutronix.de; Thu, 13 Jul 2017 18:56:05 +0200 Date: Thu, 13 Jul 2017 18:55:48 +0200 From: Alexander Dahl Message-ID: <20170713165546.GC32729@falbala.home.lespocky.de> References: MIME-Version: 1.0 In-Reply-To: Subject: Re: [ptxdist] changing fakeroot-1.14.4/configure file for ptxdist-2015.05.0 List-Id: PTXdist Development Mailing List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: ptxdist@pengutronix.de Content-Type: multipart/mixed; boundary="===============1646687080==" Errors-To: ptxdist-bounces@pengutronix.de Sender: "ptxdist" To: ptxdist@pengutronix.de --===============1646687080== Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="J5MfuwkIyy7RmF4Q" Content-Disposition: inline --J5MfuwkIyy7RmF4Q Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hei hei, On Thu, Jul 13, 2017 at 05:24:57PM +0530, Amar kumar Nandan wrote: > I want to change configure file for fakeroot-1.14.4. > I am using ptxdist (ptxdist-2015.05.0) to manage fakeroot-1.14.4. You may want to migrate your BSP to ptxdist-2017.06.0 =E2=80=A6 > How/where can I change ptxdist to modify fakeroot-1.14.4/configure file. > I want change such as replacing gcc to gcc-5 regardless of system defined > gcc. You can patch packages. If you look into the distributed files you see a folder patches containing subfolders and a series file for each. So the recommended way to go (which also is helpful if you want to upgrade a patch series for upstreaming) is: * in your BSP create a subfolder named 'patches' * inside 'patches' create a folder named _exactly_ like the one for the package you want to patch in platform-*/build-target/ * go into that folder and touch a file 'series' * in your BSP call `ptxdist clean ` * then call `ptxdist --git extract ` * go into platform-*/build-target/ * make your changes * commit those with git * call `git ptx-patches` * you'll find updated patches in the patches folder * proceed with the usual build steps IIRC there's also a chapter about patch management in the documentation. Greets Alex --=20 =C2=BBWith the first link, the chain is forged. The first speech censured,= =20 the first thought forbidden, the first freedom denied, chains us all=20 irrevocably.=C2=AB (Jean-Luc Picard, quoting Judge Aaron Satie) *** GnuPG-FP: C28E E6B9 0263 95CF 8FAF 08FA 34AD CD00 7221 5CC6 *** --J5MfuwkIyy7RmF4Q Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAABCAAGBQJZZ6YSAAoJEDStzQByIVzGV5IQAKdGWYrYJ+qM5QcsdAy5OI6R iA1jnSnGg7i7bhcDIOq9yf3VAxNF3h+2mCdeRd9GQJBU95PYhsrmrsNHtlPHu3zO 7RQG6iRA8LYJIS7Pw8lbnatogUNImU0BqqWRPN5XQZ4++/o3m2QNILeVeWM3J8ao QYU5bkijD+9Gb9ySESbjF8zJekNV0zm9Ty1vzUIeX50+h/NO2rt1cR6wnfhHQcZ0 sX7ajWuNjcIcxvLuMnY00KS0cdc+HpYU+rl5TDN9VxOqaUFTgVw0W1y+KhlRWTtR VHO1775VVIz2XeVt7QRP+4bnnzVDVcjlqH+OTVXrWCWBjp9XtM8PfiwAnMUUpqE+ ehD2CdvSS8np87B4s3tmfxdsHHTR3YVPcE7kxCjHsMVXWWRu6XFT9mpu0+b4qh5F gRxZ6P9oTxKIyB1gvoMxbF7WkhOxoFdVll2pb6eHHYTG61xfXWuVLImTxjRZVnFp ojM7hL68qPsW5bPY5qDIQAbZAFbfZIGmM/Io54bZCLKCHocyofRagmlOMtf2mdKn VImnx04bTHY6q2bHoO3SEUMwx/fnmNBXiy3Gb1W6iYXx5wlDWtmL7uZJ7QO6F1r+ dTP65i/lAJ0lY7jVrtC3Eao1f6NDX1Fnc1+a6PBQf7cQWsGTezuqS+r8vgyKLzu/ Q31+Y2+WyWUTOrlCwbhp =qmqS -----END PGP SIGNATURE----- --J5MfuwkIyy7RmF4Q-- --===============1646687080== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KcHR4ZGlzdCBt YWlsaW5nIGxpc3QKcHR4ZGlzdEBwZW5ndXRyb25peC5kZQ== --===============1646687080==--