From: Jan Kiszka <jan.kiszka@siemens.com>
To: vijai kumar <vijaikumar.kanagarajan@gmail.com>,
isar-users <isar-users@googlegroups.com>,
Baurzhan Ismagulov <ibr@radix50.net>
Subject: Re: [PATCH v4 2/2] meta: cache deb srcs as part of postprocessing
Date: Wed, 15 Apr 2020 09:28:33 +0200 [thread overview]
Message-ID: <09bbc9ef-8200-73cb-452d-4a77d28afc27@siemens.com> (raw)
In-Reply-To: <CALLGG_JdqooStOBWTXEPPSsEYgMaivEeoy-0eY4QUw35Kf0NFA@mail.gmail.com>
On 15.04.20 08:44, vijai kumar wrote:
> Hi Baurzhan,
>
> Is the below okay? Or should I send that with the new debsrc series?
I would say add a full feature first because Isar users cannot really
benefit from the series on its own yet, can they?
We need a way to feed the fetched sources into a repo or a recipe that
generates a shippable OSS medium corresponding to a binary image or a
script that applies patches to the original sources so that the result
can be pushed to OSS license scanners. I.e. we need an in-tree use case
with a test case.
Jan
>
> Thanks,
> Vijai Kumar K
>
> On Wed, Apr 8, 2020 at 7:02 PM vijai kumar
> <vijaikumar.kanagarajan@gmail.com> wrote:
>>
>> On Wed, Apr 8, 2020 at 3:34 PM vijai kumar
>> <vijaikumar.kanagarajan@gmail.com> wrote:
>>>
>>> On Wed, Apr 8, 2020 at 1:43 PM Baurzhan Ismagulov <ibr@radix50.net> wrote:
>>>>
>>>> Hello Vijai Kumar,
>>>>
>>>> On Tue, Apr 07, 2020 at 02:40:09AM -0700, vijai kumar wrote:
>>>>> There is atleast one issue in this series. Need to take care when
>>>>> HOST_DISTRO!=DISTRO. Issue first identified in rpi-stretch cross
>>>>> compilation.
>>>>
>>>> Do I understand correctly, I should wait for v5?
>>>
>>> Yes Baurzhan.
>>
>> Hi Baurzhan,
>>
>> On a second thought, I believe deb src caching can be addressed in a
>> separate series. I see that a couple of more patches would be needed
>> apart from the P2 of this series. P1 can be merged, if there are no
>> review comments though. It is a feature by itself and has no hard
>> dependency on deb-src series as such.
>>
>> I will start a separate series for src caching taking into account the
>> review comments gotten so far. Please let me know if this is ok.
>>
>> Thanks,
>> Vijai Kumar K
>>
>>>
>>>>
>>>> With kind regards,
>>>> Baurzhan.
>>>>
>>>> --
>>>> You received this message because you are subscribed to the Google Groups "isar-users" group.
>>>> To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
>>>> To view this discussion on the web visit https://groups.google.com/d/msgid/isar-users/20200408081315.hb3m2vrs5bbtnoif%40yssyq.m.ilbers.de.
>
--
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2020-04-15 7:28 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-06 14:06 [PATCH] rootfs: Make rootfs_postprocess_finalize the last step Vijai Kumar K
2020-02-06 17:21 ` Jan Kiszka
2020-02-06 17:47 ` vijai kumar
2020-02-06 18:09 ` Jan Kiszka
2020-02-06 18:28 ` vijai kumar
2020-02-10 5:37 ` [PATCH v2] rootfs: Make rootfs finalize a separate task Vijai Kumar K
2020-02-11 11:38 ` Henning Schild
2020-02-11 14:14 ` vijai kumar
2020-02-11 15:20 ` Henning Schild
2020-02-11 18:07 ` Jan Kiszka
2020-02-13 10:08 ` [PATCH v2 1/2] " Vijai Kumar K
2020-02-13 10:08 ` [PATCH v2 2/2] meta: cache deb srcs as part of postprocessing Vijai Kumar K
2020-02-14 5:48 ` [PATCH v3 1/2] rootfs: Make rootfs finalize a separate task Vijai Kumar K
2020-02-14 5:48 ` [PATCH v3 2/2] meta: cache deb srcs as part of postprocessing Vijai Kumar K
2020-02-14 8:19 ` Jan Kiszka
2020-02-14 8:41 ` vijai kumar
2020-02-14 8:45 ` vijai kumar
2020-03-11 7:16 ` [PATCH v3 1/2] rootfs: Make rootfs finalize a separate task vijai kumar
2020-04-01 7:25 ` vijai kumar
2020-04-01 8:19 ` Henning Schild
2020-04-01 10:29 ` vijai kumar
2020-04-03 6:50 ` vijai kumar
2020-04-03 8:30 ` Baurzhan Ismagulov
2020-04-03 8:50 ` vijai kumar
2020-04-03 13:05 ` [PATCH v4 " Vijai Kumar K
2020-04-03 13:05 ` [PATCH v4 2/2] meta: cache deb srcs as part of postprocessing Vijai Kumar K
2020-04-07 6:44 ` Jan Kiszka
2020-04-07 6:58 ` vijai kumar
2020-04-07 7:04 ` Jan Kiszka
2020-04-07 7:59 ` vijai kumar
2020-04-07 8:38 ` Jan Kiszka
2020-04-07 9:08 ` vijai kumar
2020-04-07 9:40 ` vijai kumar
2020-04-08 8:13 ` Baurzhan Ismagulov
2020-04-08 10:04 ` vijai kumar
2020-04-08 13:32 ` vijai kumar
2020-04-15 6:44 ` vijai kumar
2020-04-15 7:28 ` Jan Kiszka [this message]
2020-04-15 13:20 ` vijai kumar
2020-04-15 13:44 ` Jan Kiszka
2020-04-08 10:04 ` Henning Schild
2020-04-08 10:37 ` vijai kumar
2020-04-08 12:30 ` Henning Schild
2020-04-15 12:29 ` vijai kumar
2020-04-15 18:19 ` Henning Schild
2020-04-16 15:57 ` vijai kumar
2020-04-16 17:29 ` Henning Schild
2020-04-07 6:19 ` [PATCH v3 1/2] rootfs: Make rootfs finalize a separate task vijai kumar
2020-04-07 6:45 ` Jan Kiszka
2020-04-07 6:53 ` vijai kumar
2020-04-07 7:12 ` Baurzhan Ismagulov
2020-04-07 8:04 ` vijai kumar
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=09bbc9ef-8200-73cb-452d-4a77d28afc27@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=ibr@radix50.net \
--cc=isar-users@googlegroups.com \
--cc=vijaikumar.kanagarajan@gmail.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