From: Henning Schild <henning.schild@siemens.com>
To: "[ext] Claudius Heine" <claudius.heine.ext@siemens.com>,
Alexander Smirnov <asmirnov@ilbers.de>
Cc: isar-users <isar-users@googlegroups.com>
Subject: Re: Multi repo support
Date: Thu, 1 Feb 2018 19:34:58 +0100 [thread overview]
Message-ID: <20180201193458.24b6ac3f@mmd1pvb1c.ad001.siemens.net> (raw)
In-Reply-To: <20180201161658.6b0af973@mmd1pvb1c.ad001.siemens.net>
Am Thu, 1 Feb 2018 16:16:58 +0100
schrieb "[ext] Henning Schild" <henning.schild@siemens.com>:
> Am Thu, 1 Feb 2018 15:54:26 +0100
> schrieb "[ext] Claudius Heine" <claudius.heine.ext@siemens.com>:
>
> > 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.
We will also need a way to tell apt the priorities of these repos.
Multistrap just adds them and apt-get installs packages according to
its default behavior.
That means that a package with the same name and version will get
picked from a "random" repo. Overlays will need to make sure to always
have a greater version or we will need apt configuration.
https://wiki.debian.org/AptPreferences
The big question here is how/whether multistrap will handle apt
preference.
Alex already ran into that when he wanted to modify "hello". Renaming
packages - like Alex suggested - is not the way to go. Because the ones
we do overlay could be deps of packages we do not overlay.
Henning
> > Comments are welcome.
>
> Sounds good to me, cant wait to review the first patches ;).
>
> Henning
>
> > Cheers,
> > Claudius
> >
>
next prev parent reply other threads:[~2018-02-01 18:34 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 [this message]
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
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=20180201193458.24b6ac3f@mmd1pvb1c.ad001.siemens.net \
--to=henning.schild@siemens.com \
--cc=asmirnov@ilbers.de \
--cc=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