From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6517599416265736192 X-Received: by 10.80.202.11 with SMTP id d11mr13653067edi.9.1517510083421; Thu, 01 Feb 2018 10:34:43 -0800 (PST) X-BeenThere: isar-users@googlegroups.com Received: by 10.80.204.215 with SMTP id b23ls215081edj.8.gmail; Thu, 01 Feb 2018 10:34:42 -0800 (PST) X-Google-Smtp-Source: AH8x226LUofwZnuY6LrIDwDplQ7qyLo+oLahXGbmhLsJ8eEvfYIWvsWwj1MY+rr9Ll8Oq1spjC1J X-Received: by 10.80.201.74 with SMTP id p10mr13657898edh.7.1517510082873; Thu, 01 Feb 2018 10:34:42 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1517510082; cv=none; d=google.com; s=arc-20160816; b=H47sSadjjD3WOAsEKfb60X8KbmCSr+4LkxDodrlI4yAi6uiypS7+bdJLJ+RxM+JY1v 2xrsJjR5wVrAQ2Q28RE+q0ldqNStia8XJ97F4JRDZxbq+P1roSbS2iLpJB4rnOn9ZdYr VHUDq95DnIdc26cmcEgTjrByDeQxbgc9UPOtloCI2tnL8kOE2bxlFN7GUuRsQEY/rAd7 sbANPlBcZJnvORMibLGnD1IuUb/IbZOVZ27Ak3gTnmF10RVN1bjtc0FkEw4VOSF7IhK8 BSkJKVDB18jdAnb/gr6IjM3L8vqcgokIsbpcdGa5yatSLYl1OBeGhHrDH9t4ZrlJTYeJ 73CQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:subject:cc:to:from:date:arc-authentication-results; bh=SR+xRbifA718lNgL2gyB6WWamulXPkeHrbEx9Da7ec4=; b=YaaEebek/lGVn08Ln/d0EZzrR0sNXe3eSSB6BfLA2Od5VLtt27uVcA9pK6sjxW6PNI 5Zl43dDZg0Q24gkzXHcdlZ7z0jNWXbdEYq509qB/mS/Bb28W1e/P75NhQblOy1CJp96J cdsKkT0n/J72YrOACYlKvSF3tDQMdJzyw5Bum1PCQhnZYZ0mUyqzFLLJiA5KcDKUTGOh PoGomtPISKpTd/rTR0jnVlR2HLE7NPJ07OeUmmX2wSt68SXVqmUzDEtPEsppmshs/EJX XUU10P1yZiI7J527W5uD5fE4w8/LaCkLc3Z69lgokHIadZWlp5T7UvmqLGG620QQ9rhA eDiA== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=pass (google.com: domain of henning.schild@siemens.com designates 192.35.17.2 as permitted sender) smtp.mailfrom=henning.schild@siemens.com Return-Path: Received: from thoth.sbs.de (thoth.sbs.de. [192.35.17.2]) by gmr-mx.google.com with ESMTPS id v28si32843edd.3.2018.02.01.10.34.42 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 01 Feb 2018 10:34:42 -0800 (PST) Received-SPF: pass (google.com: domain of henning.schild@siemens.com designates 192.35.17.2 as permitted sender) client-ip=192.35.17.2; Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of henning.schild@siemens.com designates 192.35.17.2 as permitted sender) smtp.mailfrom=henning.schild@siemens.com Received: from mail3.siemens.de (mail3.siemens.de [139.25.208.14]) by thoth.sbs.de (8.15.2/8.15.2) with ESMTPS id w11IYg6x023357 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Thu, 1 Feb 2018 19:34:42 +0100 Received: from mmd1pvb1c.ad001.siemens.net ([167.87.78.7]) by mail3.siemens.de (8.15.2/8.15.2) with ESMTP id w11IYfbc003775; Thu, 1 Feb 2018 19:34:42 +0100 Date: Thu, 1 Feb 2018 19:34:58 +0100 From: Henning Schild To: "[ext] Claudius Heine" , Alexander Smirnov Cc: isar-users Subject: Re: Multi repo support Message-ID: <20180201193458.24b6ac3f@mmd1pvb1c.ad001.siemens.net> In-Reply-To: <20180201161658.6b0af973@mmd1pvb1c.ad001.siemens.net> References: <7714f0e1-aaca-add2-eabc-738d4043c21c@siemens.com> <20180201161658.6b0af973@mmd1pvb1c.ad001.siemens.net> X-Mailer: Claws Mail 3.15.0-dirty (GTK+ 2.24.31; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-TUID: GwmAZ3KOrEj9 Am Thu, 1 Feb 2018 16:16:58 +0100 schrieb "[ext] Henning Schild" : > Am Thu, 1 Feb 2018 15:54:26 +0100 > schrieb "[ext] Claudius Heine" : > > > 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 > > >