mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Michael Olbrich <m.olbrich@pengutronix.de>
To: Alexander Dahl <ada@thorsis.com>
Cc: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [RFC 3/4] libptxdist: add a function to find unreferenced source directories
Date: Wed, 4 Sep 2019 15:05:04 +0200	[thread overview]
Message-ID: <20190904130504.5cp7hzodc4u4egn6@pengutronix.de> (raw)
In-Reply-To: <2927514.lnS8Y61pnd@ada>

On Fri, Aug 23, 2019 at 11:01:58AM +0200, Alexander Dahl wrote:
> Hei hei,
> 
> Am Freitag, 23. August 2019, 10:33:42 CEST schrieb Roland Hieber:
> > On Thu, Aug 22, 2019 at 05:38:19PM +0200, Michael Olbrich wrote:
> > > On Thu, Aug 22, 2019 at 12:42:40PM +0200, Roland Hieber wrote:
> > > > +
> > > > +	# get list of dirs for which no package exists
> > > > +	comm --nocheck-order -13 ${pkgslistfile} ${patchdirfile} | while 
> read
> > > > dir; do +		ptxd_in_path PTXDIST_PATH_PATCHES ${dir}
> > > > +		ptxd_print_path ${ptxd_reply}
> > > > +	done | while read line; do
> > > > +		# annotate packages that are built specially or their version
> > > > +		# depends on enabling kconfig entries
> > > > +		case i in
> > > > +			*alsa-lib*|*at91bootstrap*|*barebox*)
> > > 
> > > I think we can 'fix' the alsa-lib false positives.
> > > And maybe we should just remove the at91bootstrap patches, they are really
> > > old anyways.
> > > But why barebox? There should be no old patches, right?
> > 
> > Ah, yes. I was thinking at91bootstrap can be disabled, so the version
> > number is empty, and the same can be said for barebox too. But the only
> > location where Barebox patches occur is at the BSP level, and I guess
> > it doesn't happen that someone switches from barebox to at91bootstrap
> > with patches lying around locally.
> 
> FWIW, we are still using different versions of at91bootstrap in different 
> BSPs. The legacy version (at91bootstrap) has patches in the directory 
> 'patches/Bootstrap-v1.16' and the current version (at91bootstrap2) has them in 
> 'patches/at91bootstrap-3.8.13'.
> 
> If one or the other package needs fixes, let me know.

PTXdist upstream has patches for 'at91bootstrap'. Do you use those, or do
you have your own patch stack in your BSP?

I'd like to remove the patches from PTXdist. It's the only packages that
has a configurable version and patches for one specific version upstream.

Michael

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de

  reply	other threads:[~2019-09-04 13:05 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-22 10:42 [ptxdist] [RFC 1/4] patches/HEADER: remove apparently outdated and unreferenced file Roland Hieber
2019-08-22 10:42 ` [ptxdist] [RFC 2/4] Makefile.in: sort environment tools alphabetically Roland Hieber
2019-08-22 10:42 ` [ptxdist] [RFC 3/4] libptxdist: add a function to find unreferenced source directories Roland Hieber
2019-08-22 10:53   ` Roland Hieber
2019-08-22 12:43   ` Uwe Kleine-König
2019-08-22 15:38   ` Michael Olbrich
2019-08-23  8:33     ` Roland Hieber
2019-08-23  9:01       ` Alexander Dahl
2019-09-04 13:05         ` Michael Olbrich [this message]
2019-09-04 13:16           ` Alexander Dahl
2019-09-09  6:23             ` Michael Olbrich
2019-09-09  7:46               ` Alexander Dahl
2019-09-09 20:33                 ` Ladislav Michl
2019-09-10  8:13                   ` Michael Olbrich
2019-08-22 10:42 ` [ptxdist] [RFC 4/4] ptxdist: add a 'lint' subcommand Roland Hieber
2019-08-22 11:44 ` [ptxdist] [RFC 1/4] patches/HEADER: remove apparently outdated and unreferenced file Robert Schwebel

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=20190904130504.5cp7hzodc4u4egn6@pengutronix.de \
    --to=m.olbrich@pengutronix.de \
    --cc=ada@thorsis.com \
    --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