From: Baurzhan Ismagulov <ibr@radix50.net>
To: isar-users@googlegroups.com
Subject: Re: [PATCH] Introduce SCRIPTSDIR variable
Date: Sun, 5 Apr 2020 18:49:43 +0200 [thread overview]
Message-ID: <20200405164943.mccmlrje526qxyw3@yssyq.m.ilbers.de> (raw)
In-Reply-To: <20200128193520.26504-1-Vijaikumar_Kanagarajan@mentor.com>
Hello Vijai Kumar,
On Wed, Jan 29, 2020 at 01:05:20AM +0530, Vijai Kumar K wrote:
> ISARROOT is mostly used with wic implemetation for the scripts
> directory. Introduce SCRIPTSDIR to satisfy wic.
>
> When ISARROOT equivalent is needed, derive it from SCRIPTSDIR.
Thanks for pursuing this annoying issue. I like the concept of having a special
variable for the directory. The advantage is that the code doesn't rely on a
specific directory structure.
Now the patch fails to apply upon d90c2ab "wic-img: allow wic to find bitbake
binary", submitted shortly before yours. Looking at both together, I realize
that deriving the ISARROOT equivalent from SCRIPTSDIR makes it rely on the
directory structure again.
One possibilty would be to introduce both SCRIPTSDIR and the ISARROOT
equivalent (calling it e.g. ISARDIR). What do you think?
With kind regards,
Baurzhan.
next prev parent reply other threads:[~2020-04-05 16:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-28 19:35 Vijai Kumar K
2020-01-28 21:43 ` Henning Schild
2020-01-29 6:22 ` Vijai Kumar K
2020-02-18 6:05 ` vijai kumar
2020-04-05 16:49 ` Baurzhan Ismagulov [this message]
2020-04-06 8:30 ` vijai kumar
2020-04-23 14:56 ` vijai kumar
2020-04-27 9:11 ` [PATCH v2] Replace ISARROOT with more relevant variables Vijai Kumar K
2020-04-27 10:22 ` vijai kumar
2020-04-27 10:28 ` [PATCH v3] " Vijai Kumar K
2020-05-26 2:54 ` vijai kumar
2020-05-26 7:51 ` Baurzhan Ismagulov
2020-05-28 5:28 ` vijai kumar
2020-09-16 19:11 ` Baurzhan Ismagulov
2020-09-17 2:45 ` 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=20200405164943.mccmlrje526qxyw3@yssyq.m.ilbers.de \
--to=ibr@radix50.net \
--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