mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Alexander Dahl <post@lespocky.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] changing fakeroot-1.14.4/configure file for ptxdist-2015.05.0
Date: Thu, 13 Jul 2017 18:55:48 +0200	[thread overview]
Message-ID: <20170713165546.GC32729@falbala.home.lespocky.de> (raw)
In-Reply-To: <CAExv3aJ4-De4ZYzo_KdVkGivJ+d1mwPcOfk_5cSnNr2_5h-gwg@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1602 bytes --]

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 …

> 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 <yourpackage>`
* then call `ptxdist --git extract <yourpackage>`
* go into platform-*/build-target/<yourpackage>
* 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

-- 
»With the first link, the chain is forged. The first speech censured, 
the first thought forbidden, the first freedom denied, chains us all 
irrevocably.« (Jean-Luc Picard, quoting Judge Aaron Satie)
*** GnuPG-FP: C28E E6B9 0263 95CF 8FAF  08FA 34AD CD00 7221 5CC6 ***

[-- Attachment #1.2: Type: application/pgp-signature, Size: 819 bytes --]

[-- Attachment #2: Type: text/plain, Size: 91 bytes --]

_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de

  reply	other threads:[~2017-07-13 16:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-13 11:54 Amar kumar Nandan
2017-07-13 16:55 ` Alexander Dahl [this message]
2017-07-14  8:42   ` Roland Hieber

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170713165546.GC32729@falbala.home.lespocky.de \
    --to=post@lespocky.de \
    --cc=ptxdist@pengutronix.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox