From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6520199916203016192 X-Received: by 10.46.85.25 with SMTP id j25mr110950ljb.43.1518431245987; Mon, 12 Feb 2018 02:27:25 -0800 (PST) X-BeenThere: isar-users@googlegroups.com Received: by 10.25.151.15 with SMTP id z15ls1265549lfd.14.gmail; Mon, 12 Feb 2018 02:27:23 -0800 (PST) X-Google-Smtp-Source: AH8x2245XjrJjI2PZa/su/97E+NScgJnYd5ZLoLUivsDXGi46Hd4aV3O/WivKmWrbxzQxpzK5Y4x X-Received: by 10.25.150.9 with SMTP id y9mr761642lfd.7.1518431243860; Mon, 12 Feb 2018 02:27:23 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1518431243; cv=none; d=google.com; s=arc-20160816; b=jpQuGWx6AJV/RU/N8kYTo6Yf0a6zAkPVp0BjbSNdkz8rKdlJgUqydRC0OtGOyVJjA/ rvqbIiB1uupcognAlHEV4BnFsrxI2yKTMLQzIIEMrnUbjl5vNZR+Jj/fB/x0EafgCsy5 i7+Pf/Epw+82If6CgnG5P31h97fjsNxtZbpcjYwX5uSbB0vkLciSC9HpTiKoEXHW273Y jk7UqqrZpWbqp0C2ntwYDjOgKb+cBLjfm93mGRBFr+030R/ORhy0ydps50PO2dd2d+tC qhGCgVAKjqg+Cvw70alDFMlq6gsa5d7K+m/trDGXD+U9Np9UV6fy/Bpm+pqc8WUx1Vh2 rgaA== 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:references:to:from:subject :arc-authentication-results; bh=W3a+NySxU7Og6flb1Oa71/1N61N6+nQJTWw6m3FkVZw=; b=ezgllXoc4HLaSAPHoFCDcZbPiTzO9LDhmElaIgGogqBJAFx6GQ2HXvMVeID+nC6gaJ EJ6D+FWpXPicxXexEj8xr2xvIDVo7Mtc5ZvsvBAcjrwZZbtIYHSWROEXkaidikGRkZ/c 5f4pDCVbYOcBOpwvddC0buRwCK4nYI+H8lxpr0CxZY6F35GnxxxEbmafk267YwcYKDdu 1KtCzWmO3Zof1L4GF/9W/nRj0ZY+cCo/OpNRY96+rwTyGlV5dU/86lr+HYuqtV2wav20 r8A0CMoKXPA0d31xIwLw9NHEPTFMr46RpsdMeQLphr7kSt+3Oz8sMXXOgxds083CjMJc Xmlg== 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 u10si457810lju.0.2018.02.12.02.27.23 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 12 Feb 2018 02:27:23 -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 mail3.siemens.de (mail3.siemens.de [139.25.208.14]) by thoth.sbs.de (8.15.2/8.15.2) with ESMTPS id w1CARNEf000709 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Mon, 12 Feb 2018 11:27:23 +0100 Received: from [139.25.68.37] (md1q0hnc.ad001.siemens.net [139.25.68.37] (may be forged)) by mail3.siemens.de (8.15.2/8.15.2) with ESMTP id w1CARMdi002999; Mon, 12 Feb 2018 11:27:23 +0100 Subject: Re: [PATCH v4 2/8] Prioritize isar-apt repo over all others From: Jan Kiszka To: Alexander Smirnov , isar-users References: <136df397-5fce-9f50-fd74-f35f038fbda2@siemens.com> Message-ID: <905dabd5-e9b9-9382-8c86-8e33d8559b21@siemens.com> Date: Mon, 12 Feb 2018 11:27:21 +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: 7bit X-TUID: RNz6MNT5gGf3 On 2018-02-12 11:11, Jan Kiszka wrote: > On 2018-02-12 11:08, Alexander Smirnov wrote: >> On 02/12/2018 12:41 PM, Jan Kiszka wrote: >>> On 2018-02-12 10:33, Alexander Smirnov wrote: >>>> On 02/11/2018 06:25 PM, Jan Kiszka wrote: >>>>> From: Jan Kiszka >>>>> >>>>> This ensures that we can override packages from upstream Debian or >>>>> other >>>>> external sources with our self-built versions. We achieve this for now >>>>> by asking multistrap to drop a preferences file for the buildchroot so >>>>> that dependency installations use the right priority. For the image >>>>> build, this does not work because all packages are pull during the >>>>> bootstrap. Therefore, we set aptdefaultrelease to isar to ensure that >>>>> our repo gets the higher priority. >>>>> >>>> >>>> I'm not sure that I completely understand this. What is the use-case for >>>> this? If you build your own copy of upstream package, this >>>> prioritization could be resolved by specifying suffix to version. >>> >>> Simple example: custom kernel build of linux-cip >>> >>> This generates a package called linux-image-amd64 (for amd64 as target), >>> and that may have a version < debian's kernel. Now, if we do not >>> prioritize isar-apt over upstream, the upstream kernel is taken, even >>> when you switched PREFERRED_PROVIDER (in fact, the build will break when >>> that virtual package linux-cip is selected but can't be installed due to >>> the version preference "newest"). >> >> Ok, but why you can't name you kernel 'linux-cip-image-amd64'? Having >> the same name as with original Debian one could be confusing. >> > > That is mandatory, in order to write packages that depend on THE kernel, > instead of "my-custom-kernel-in-version-4.4.112". To make it clearer, just look at the example-module case: The recipe can build both against the distro as well as all custom kernels, without touching it. And that is a pattern not limited to kernel<->module relationships. Jan -- Siemens AG, Corporate Technology, CT RDA IOT SES-DE Corporate Competence Center Embedded Linux