From: Claudius Heine <claudius.heine.ext@siemens.com>
To: isar-users <isar-users@googlegroups.com>
Subject: Re: Multi repo support
Date: Wed, 7 Feb 2018 10:05:07 +0100 [thread overview]
Message-ID: <b6fe3576-9602-e3a8-8096-cff20b761792@siemens.com> (raw)
In-Reply-To: <7714f0e1-aaca-add2-eabc-738d4043c21c@siemens.com>
Hi,
On 02/01/2018 03:54 PM, [ext] Claudius Heine wrote:
> Hi,
>
> I would like to start the discussion about how to best implement muti
> repository support in isar.
>
> Does someone already has some ideas or even something in the pipeline
> for this?
>
> If not then I do have an idea that was outlined together with Jan:
>
> Adding and configuring apt repositories should be done via config files.
> It should be possible to define own multiconfigs while including
> multiconfigs from other layers. These configs then append filepaths to a
> global variable.
>
> Every file that is added this way contains 'sources.list' compatible
> repository definitions. So one repo each line.
>
> For every line in those files a repository entry for multistrap.conf is
> created. Here we might need some more complex code to convert such a apt
> repo tripel to the right format multistrap expects. But by using the
> 'sources.lists' format we would be independent of multistrap and become
> more future proof.
>
> Comments are welcome.
So for reference here are the points gathered from the comments in this
thread:
- It needs some way to handle package name collision. For instance if
custom packages have the same name as an upstream package.
Suggestion: Use apt-preferences to prefer packages from the 'isar'
repo. To consider: How to teach multistrap about those
preferences?
- Overwriting source entries with local mirrors.
Suggestion: Similar to how oe does it with PREMIRRORS.
e.g. DEBIAN_APT_MIRROR_append = "regex replace\n"
To be implemented later.
Cheers,
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
next prev parent reply other threads:[~2018-02-07 9:05 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-01 14:54 Claudius Heine
2018-02-01 15:16 ` Henning Schild
2018-02-01 18:34 ` Henning Schild
2018-02-01 18:51 ` Claudius Heine
2018-02-01 20:47 ` Alexander Smirnov
2018-02-01 21:07 ` Claudius Heine
2018-02-01 21:52 ` Alexander Smirnov
2018-02-02 6:40 ` Claudius Heine
2018-02-02 12:28 ` Alexander Smirnov
2018-02-02 13:26 ` Claudius Heine
2018-02-02 13:48 ` Alexander Smirnov
2018-02-02 14:15 ` Claudius Heine
2018-02-02 14:36 ` Alexander Smirnov
2018-02-02 15:36 ` Claudius Heine
2018-02-07 9:05 ` Claudius Heine [this message]
2018-02-07 9:21 ` Jan Kiszka
2018-02-07 9:25 ` Claudius Heine
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=b6fe3576-9602-e3a8-8096-cff20b761792@siemens.com \
--to=claudius.heine.ext@siemens.com \
--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