DistroKit Mailinglist
 help / color / mirror / Atom feed
From: Alexander Dahl <ada@thorsis.com>
To: distrokit@pengutronix.de
Subject: Re: [DistroKit] Multiple identical barebox source trees
Date: Fri, 22 Nov 2019 08:25:29 +0100	[thread overview]
Message-ID: <1712454.3hirt1jDJJ@ada> (raw)
In-Reply-To: <20191121133703.5boamtmib4nmgyxm@pengutronix.de>

Hello,

Am Donnerstag, 21. November 2019, 14:37:03 CET schrieb Michael Olbrich:
> On Tue, Nov 19, 2019 at 10:33:42AM +0100, Alexander Dahl wrote:
> > Is it possible with ptxdist to also share the source tree? That could save
> > some time for unpacking and patching, right?
> 
> It's not really possible in a sane way. The Problem is, how would 'clean'
> for one of the barebox packages work? It's not really clean, when the
> source is not deleted.

Why not delete the common source then? Clean of one package would clean the 
common source folder, all depending packages would have to be rebuilt. 

A


_______________________________________________
DistroKit mailing list
DistroKit@pengutronix.de

      reply	other threads:[~2019-11-22  7:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-19  9:33 Alexander Dahl
2019-11-21 13:37 ` Michael Olbrich
2019-11-22  7:25   ` Alexander Dahl [this message]

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=1712454.3hirt1jDJJ@ada \
    --to=ada@thorsis.com \
    --cc=distrokit@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