From: Jan Kiszka <jan.kiszka@siemens.com>
To: Alexander Smirnov <asmirnov@ilbers.de>,
isar-users <isar-users@googlegroups.com>
Subject: Re: [PATCH 2/6] Add clean and cleanall tasks
Date: Tue, 13 Feb 2018 13:51:40 +0100 [thread overview]
Message-ID: <bfc5fa18-ea2f-c974-4cf3-e5fff15cb3a3@siemens.com> (raw)
In-Reply-To: <a51e803e-7155-57c5-3109-806821132449@ilbers.de>
On 2018-02-13 13:49, Alexander Smirnov wrote:
> On 02/12/2018 10:59 AM, Jan Kiszka wrote:
>> From: Jan Kiszka <jan.kiszka@siemens.com>
>>
>> Derived from OE, this adds clean and cleanall tasks for Isar. The clean
>> task comes with CLEANFUNCS hook, we just run them prior to cleaning the
>> WORKDIR. This is used by dpkg-base to remove all packages from isar-apt
>> that the build may have deployed.
>>
>> As we are at it, also do a repo clean prior to deploying a package -
>> just in case something triggers a partial rebuild without prior
>> cleaning...
>>
>
> Very good! :-)
>
> I think, we also should erase the package's "PROVIDES" from buildchroot
> (like libhello-dev). This could be implemented later in next series.
Good point. Will try to look into that later.
Jan
--
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2018-02-13 12:51 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-12 7:59 [PATCH 0/6] Add support for automatic partial rebuilds on recipe changes Jan Kiszka
2018-02-12 7:59 ` [PATCH 1/6] Fix indention of base_do_build Jan Kiszka
2018-02-12 7:59 ` [PATCH 2/6] Add clean and cleanall tasks Jan Kiszka
2018-02-13 12:49 ` Alexander Smirnov
2018-02-13 12:51 ` Jan Kiszka [this message]
2018-02-12 7:59 ` [PATCH 3/6] Enable recipe caching Jan Kiszka
2018-02-12 7:59 ` [PATCH 4/6] Enable proper rebuilds on dependency changes Jan Kiszka
2018-02-13 13:03 ` Alexander Smirnov
2018-02-13 16:21 ` Jan Kiszka
2018-02-13 17:57 ` Jan Kiszka
2018-02-13 18:08 ` Alexander Smirnov
2018-02-13 18:44 ` Jan Kiszka
2018-02-13 19:02 ` Alexander Smirnov
2018-02-13 19:22 ` Jan Kiszka
2018-02-13 19:38 ` Alexander Smirnov
2018-02-13 20:04 ` Jan Kiszka
2018-02-12 7:59 ` [PATCH 5/6] dpkg-raw: Clean DEBIAN dir prior to filling it Jan Kiszka
2018-02-13 14:06 ` Alexander Smirnov
2018-02-13 16:22 ` Jan Kiszka
2018-02-13 16:31 ` Alexander Smirnov
2018-02-13 16:33 ` Jan Kiszka
2018-02-12 7:59 ` [PATCH 6/6] isar-image-base: Clean rootfs folder prior to building Jan Kiszka
2018-02-13 13:49 ` Alexander Smirnov
2018-02-13 16:24 ` Jan Kiszka
2018-02-13 7:40 ` [PATCH 0/6] Add support for automatic partial rebuilds on recipe changes Jan Kiszka
2018-02-13 14:01 ` Alexander Smirnov
2018-02-13 16:28 ` Jan Kiszka
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=bfc5fa18-ea2f-c974-4cf3-e5fff15cb3a3@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=asmirnov@ilbers.de \
--cc=isar-users@googlegroups.com \
/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