public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Raphael Lisicki <raphael.lisicki@siemens.com>,
	isar-users@googlegroups.com
Cc: Henning Schild <henning.schild@siemens.com>
Subject: Re: do_adjust_git in dpkg-base.bbclass not working for gitsm fetcher
Date: Wed, 2 Dec 2020 19:03:50 +0100	[thread overview]
Message-ID: <6df1609e-258d-3ff0-0faa-6f4950a9ef6b@siemens.com> (raw)
In-Reply-To: <6bba3846-74ef-b89f-b15e-4743ffd78287@siemens.com>

On 02.12.20 18:10, Raphael Lisicki wrote:
> Thanks for your answers. I know well about the pains of the submodules.
> 
>>
>> SRC_URI = "gitsm://foo.git;destsuffix=${P}"
>> SRCREV = "0815"
>>
>> becomes
>>
>> SRC_URI = "git://foo.git;destsuffix=${P};name=main
>> SRCREV_main = "0815"
>> SRC_URI += "git://bar.git;destsuffix=${P}/modules/bar;name=module1
>> SRC_URI += "git://baz.git;destsuffix=${P}/mod/baz;name=module2
>> SRCREV_module1 = "1234"
>> SRCREV_module2 = "abcd"
>>
> 
> This sounds like a feasible workaround. Happily, I was able to just
> switch to the git fetcher.
> 
> Simply adding "and ud.type != 'gitsm'" would also fix this for certain
> cases (mine :D ) . Given that it is known that gitsm is not working
> properly, such a best-effort fix might also be an option.
> 

Feel free to send such a trivial patch. If it makes things a bit better,
no need to not merge that.

Jan

-- 
Siemens AG, T RDA IOT
Corporate Competence Center Embedded Linux

      reply	other threads:[~2020-12-02 18:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-01 10:41 Raphael Lisicki
2020-12-01 11:41 ` Jan Kiszka
2020-12-01 15:40   ` Henning Schild
2020-12-01 16:44     ` Jan Kiszka
2020-12-01 18:51       ` Henning Schild
2020-12-02 17:10     ` Raphael Lisicki
2020-12-02 18:03       ` Jan Kiszka [this message]

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=6df1609e-258d-3ff0-0faa-6f4950a9ef6b@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=henning.schild@siemens.com \
    --cc=isar-users@googlegroups.com \
    --cc=raphael.lisicki@siemens.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