From: Claudius Heine <ch@denx.de>
To: Henning Schild <henning.schild@siemens.com>,
Jan Kiszka <jan.kiszka@siemens.com>
Cc: "[ext] claudius.heine.ext@siemens.com"
<claudius.heine.ext@siemens.com>,
isar-users@googlegroups.com
Subject: Re: [PATCH] added 'isar-cfg-userpw' package
Date: Mon, 25 Feb 2019 12:44:48 +0100 [thread overview]
Message-ID: <155109508888.4408.14951044073249892932@ardipi> (raw)
In-Reply-To: <40ca1c88-0843-5036-b9eb-c19fcd80078c@siemens.com>
[-- Attachment #1: Type: text/plain, Size: 2193 bytes --]
Quoting Jan Kiszka (2019-02-25 12:15:32)
> On 25.02.19 10:32, Henning Schild wrote:
> > Am Mon, 25 Feb 2019 09:48:38 +0100
> > schrieb "[ext] Jan Kiszka" <jan.kiszka@siemens.com>:
> >> On 25.02.19 09:44, Claudius Heine wrote:
[...]
> >>> But of course if you now have a '*-debug' and '*-release'
> >>> multiconfig, you cannot build that in parallel if one package is
> >>> build with two different variables.
> >>>
> >>> And that exactly hits the mark with the problem I have with the way
> >>> Isar uses multiconfigs and tries to share packages from different
> >>> multiconfigs.
> >>>
> >>> IMO if you want to continue doing it that way, you would need to
> >>> have a 'isar-cfg-localpurge-debug' and a 'isar-cfg-userpw-debug'.
> >>> And do that for all possible other configurations you want to build
> >>> in parallel...
> >>
> >> Awkward. We need to stop this weird patterns which require too much
> >> boilerplate recipes to achieve very simple things. Let's just make
> >> these variables per-image.
> >
> > I had a feeling that same PN-PV but different content could be a
> > problem. And here we go. But Claudius is right, either we have
> > different packages (by name and/or version) or we do not use packages
> > for such tasks. Per Image variables will not work, the last
> > do_deploy_deb will win and set the password for every image sharing the
> > repo.
>
> Right, we need to discuss about that "everything is a package" in this context.
> I may make Isar life easier, but not Isar user's life. Also, it's deviating with
> the image configuration from OE.
I now took a look exactly how OE manage that, and that seems to answer
my previous question. The implementation seems a bit complex, but I
guess that it could be adapted to fit Isars purposes.
regards,
Claudius
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-54 Fax: (+49)-8142-66989-80 Email: ch@denx.de
PGP key: 6FF2 E59F 00C6 BC28 31D8 64C1 1173 CB19 9808 B153
Keyserver: hkp://pool.sks-keyservers.net
[-- Attachment #2: signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
-----BEGIN PGP SIGNATURE-----
iQIzBAABCAAdFiEEb/LlnwDGvCgx2GTBEXPLGZgIsVMFAlxz1TAACgkQEXPLGZgI
sVNk3A//WIUtwX1eFSW3it+zdJrhdTNveAdf9svsk0pf4xAg2k2ta/ss4OuOH0xy
1DrL5AJtLZ668chq0b/5TnF7XwDkFBG2JciGxR6UBnB5TpKpkpYev6Ou3MDD+LR9
8EDpJ9HbTlZYd4Hx24TwDRyNPe4NquDn8CmMl+kLJxqlcxoGmX5cuVRvmdPfRTOz
Od+3ZoOikj9gEOwyo8tiebGuWDpdz9GikJqM9gQVFHVcroMTUZhnBsUQlQWMhJfM
pe6rC1C2DbGONBO3RfPtotcfMhFcu9gX98eqJqSyhb0McpWdQ7yIz7dsM9AvSD0t
T0M0+YrhqUBFob1EMCyeXjWfNtrqY2r7nDDJ+peRyJu5OJb7p6K1icgw8cqVMBY6
7tnDd7o0uCNVlbVRALYBrIhaX5FR2BemXr4Bx5au5nP4MAPOIvBL2DiOMGT7H+P8
IMARt64J9CfmEEcLYJNqnw5oSLzF9HdKR2iVCqLCo9ekYL9L3lo20W7YEBr4OXQ2
DUEjcrjbgFYT1f4Pt0nLAZkDdXXDN8nMxwfq2vS5ywckFSnpW7gno9YwRPAxbV3I
hluBm/n2N0aKi8v8VC7aTLq2kBdy700bhUnwCHrQLE6ZHy2cm5hVvXKnq0+/VaT6
vKEUIPzOq8COqBlrXjZfDdzRDI0Vog7EN0/ygrdmQ/NaUbwQANU=
=HZ8W
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2019-02-25 11:44 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-18 16:21 claudius.heine.ext
2019-02-18 16:58 ` Henning Schild
2019-02-19 9:19 ` Henning Schild
2019-02-23 10:42 ` Jan Kiszka
2019-02-25 8:07 ` Jan Kiszka
2019-02-25 8:44 ` Claudius Heine
2019-02-25 8:48 ` Jan Kiszka
2019-02-25 9:32 ` Henning Schild
2019-02-25 11:15 ` Jan Kiszka
2019-02-25 11:44 ` Claudius Heine [this message]
2019-03-04 10:15 ` Claudius Heine
2019-02-25 11:18 ` Claudius Heine
2019-02-25 10:18 ` Adler, Michael
2019-02-25 10:34 ` Henning Schild
2019-02-25 11:38 ` Henning Schild
2019-02-26 19:36 ` Jan Kiszka
2019-02-26 19:47 ` Jan Kiszka
2019-02-27 8:46 ` Henning Schild
2019-02-27 10:20 ` Henning Schild
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=155109508888.4408.14951044073249892932@ardipi \
--to=ch@denx.de \
--cc=claudius.heine.ext@siemens.com \
--cc=henning.schild@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@siemens.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