From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6517599416265736192 X-Received: by 10.223.142.56 with SMTP id n53mr601599wrb.20.1517995298151; Wed, 07 Feb 2018 01:21:38 -0800 (PST) X-BeenThere: isar-users@googlegroups.com Received: by 10.28.129.141 with SMTP id c135ls313266wmd.11.canary-gmail; Wed, 07 Feb 2018 01:21:37 -0800 (PST) X-Google-Smtp-Source: AH8x224+rqFljnoEEl7XIuRjLGJjbqBD6vkg31KIXoj7uo0e7JO84gtsHCnTUWua8X1VqmhqjuTG X-Received: by 10.28.106.6 with SMTP id f6mr567583wmc.20.1517995297548; Wed, 07 Feb 2018 01:21:37 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1517995297; cv=none; d=google.com; s=arc-20160816; b=lotv/GxEPqelrtJ8Rj/PtQUNQWo0l16GFaQ4cdnBKOC9X+T32f0+4Bo1RAnF7BwvDl fWkDqSlIy8sVaVnRAVr9dPLEX4cLC9CW2ovB9Ez1biUGbHSpw+kNjnlfoDq549tkJcEM L6LbRbwkp3G78cf/nZpnaop9Nev8ywSFrA4LUW5o4DGXOI5ztZeY7u63NBmUMbTeijPu BMgVRMyHHR+HUbS7BQrg3xSdwTV8x5utJEpVdvTcwX/bRCQh3aXfFyCBspSqXcrTkJun meYl+DJIbBoAmO88fYlE8ZjBdnQsOQTvamcNea+WpgsANiievCRbyix4S4h43r7iwyj3 wKUw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=content-transfer-encoding:content-language:in-reply-to:mime-version :user-agent:date:message-id:from:references:to:subject :arc-authentication-results; bh=s31C42uY7jZ6eNsExGdR5h/VdMG98WiMy7l97eD3m1M=; b=zWmezDgHtm3/OIT/IbQpf2FndM1h3GyfikeuU3Iot5C6xIgidXDIgT7OVmyMQLxdKu OxUiEkeNtdwcOFHFg7HASS6jUALOeody4MA51gGLpx6ML3BKhpqsn4cuBYQV2elGLM3b XmCrslCjO63y9ogBHGyMpdX0lv2bciw04azRHbaGdNh0X6xOTUOgJ1s2WchDrpU7f4JI rshi1zKoNVjrBDbAV3KbIbvzM6hKkfK1vpx+ndcP6YTKZM6a9B7H6JEnSw9T3D2pDZl2 whRxlbUaAPS9Y7g+39MqE2mA6NIsLB6VWGNFfsLSXk5vJDKnDjqDMNIWhUFGX1IijM+u r4YA== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=pass (google.com: domain of jan.kiszka@siemens.com designates 192.35.17.2 as permitted sender) smtp.mailfrom=jan.kiszka@siemens.com Return-Path: Received: from thoth.sbs.de (thoth.sbs.de. [192.35.17.2]) by gmr-mx.google.com with ESMTPS id v8si59911wrg.2.2018.02.07.01.21.37 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 07 Feb 2018 01:21:37 -0800 (PST) Received-SPF: pass (google.com: domain of jan.kiszka@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 jan.kiszka@siemens.com designates 192.35.17.2 as permitted sender) smtp.mailfrom=jan.kiszka@siemens.com Received: from mail1.siemens.de (mail1.siemens.de [139.23.33.14]) by thoth.sbs.de (8.15.2/8.15.2) with ESMTPS id w179LbPs010574 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Wed, 7 Feb 2018 10:21:37 +0100 Received: from [139.25.68.37] (md1q0hnc.ad001.siemens.net [139.25.68.37] (may be forged)) by mail1.siemens.de (8.15.2/8.15.2) with ESMTP id w179LYa5004750; Wed, 7 Feb 2018 10:21:35 +0100 Subject: Re: Multi repo support To: "[ext] Claudius Heine" , isar-users References: <7714f0e1-aaca-add2-eabc-738d4043c21c@siemens.com> From: Jan Kiszka Message-ID: <2d20812f-fe56-6920-e6bd-b9b523d10292@siemens.com> Date: Wed, 7 Feb 2018 10:21:34 +0100 User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); de; rv:1.8.1.12) Gecko/20080226 SUSE/2.0.0.12-1.1 Thunderbird/2.0.0.12 Mnenhy/0.7.5.666 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit X-TUID: eLIZz/RkzjFU On 2018-02-07 10:05, [ext] Claudius Heine wrote: > 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? https://manpages.debian.org/stretch/multistrap/multistrap.1.en.html#Apt_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. As discussed offline, this sounds like valuable add-on for later. Until then, the user should be able to replace repo lists that are pointing to undesired URLs with own ones with the preferred URLs. Jan -- Siemens AG, Corporate Technology, CT RDA IOT SES-DE Corporate Competence Center Embedded Linux