From: Juergen Beisert <jbe@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: [ptxdist] [PATCH] Fix some packages in regard to PTXdist's pre-build archive feature
Date: Thu, 23 Jan 2014 10:52:41 +0100 [thread overview]
Message-ID: <1390470765-9417-1-git-send-email-jbe@pengutronix.de> (raw)
Attached some patches to make the use of pre-build archives to speed up builds
possible again. I'm sure I do not catch all broken packages yet. If someone
founds a package where the targetinstall stage grabs files from the source
tree instead of the install tree, please drop me a note or send a patch
similar to mine.
Juergen
--
ptxdist mailing list
ptxdist@pengutronix.de
next reply other threads:[~2014-01-23 9:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-23 9:52 Juergen Beisert [this message]
2014-01-23 9:52 ` [ptxdist] [PATCH 1/4] QT4/pre-build: installing the examples needs the source tree Juergen Beisert
2014-01-23 10:57 ` Marc Kleine-Budde
2014-01-23 11:38 ` Juergen Beisert
2014-01-23 9:52 ` [ptxdist] [PATCH 2/4] Mono/pre-build: targetinstall needs access to " Juergen Beisert
2014-01-23 9:52 ` [ptxdist] [PATCH 3/4] bluez/pre-build: installing the test scripts needs " Juergen Beisert
2014-01-23 9:52 ` [ptxdist] [PATCH 4/4] PTXdist: be more helpful using the pre-build archive feature Juergen Beisert
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=1390470765-9417-1-git-send-email-jbe@pengutronix.de \
--to=jbe@pengutronix.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