From: Alexander Kanavin <alex.kanavin@gmail.com>
To: Patrick Huesmann <patrick.huesmann@desy.de>
Cc: yocto@lists.yoctoproject.org
Subject: Re: [yocto] dnf/libsolv vs. package feed with commit hashes in version strings
Date: Thu, 29 Feb 2024 10:48:10 +0100 [thread overview]
Message-ID: <CANNYZj8fGE=pCNSTLD8VP+xsXBZA=MYtGM5jDdnn4eG1fSHrRw@mail.gmail.com> (raw)
In-Reply-To: <23930.1709198778245848116@lists.yoctoproject.org>
On Thu, 29 Feb 2024 at 10:26, Patrick Huesmann <patrick.huesmann@desy.de> wrote:
> Your suggestion will probably get rid of a lot of complexity in our recipe that tried to work around bitbake's limitations. But I'm still not sure how to tackle the original problem (AUTOINC from PRSERV for file:// and http:// resources), even if I have SRCREV as static data before running bitbake.
>
> If I understand correctly, bb.fetch2.get_srcrev() requires that the fetcher's supports_srcrev() is set, so it wouldn't support file and http fetchers.
>
> So what would be the recommended way to implement this functionality? Should I write and somehow inject my own fetcher module, or reimplement package_get_auto_pr() for my recipe (talking to PRSERV directly)?
I know as much about this as you do. I don't have time to run
experiments, and it's hard to tell from reading the code if there's a
possible code path that would inject a value from pr server into PKGV
for non-git resources.
Maybe the easiest is to have self-contained logic in the script that
ensures PV always increases before it's set, and not try to involve pr
server in that. Writing a new fetcher is... far-fetched :)
Alex
prev parent reply other threads:[~2024-02-29 9:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-28 11:56 dnf/libsolv vs. package feed with commit hashes in version strings patrick.huesmann
2024-02-28 12:05 ` [yocto] " Alexander Kanavin
2024-02-28 12:25 ` patrick.huesmann
2024-02-28 12:51 ` Martin Jansa
2024-02-28 12:53 ` Alexander Kanavin
2024-02-28 13:17 ` patrick.huesmann
2024-02-28 13:25 ` Alexander Kanavin
2024-02-28 15:15 ` patrick.huesmann
2024-02-28 16:49 ` Alexander Kanavin
2024-02-28 17:37 ` patrick.huesmann
2024-02-28 17:54 ` Alexander Kanavin
2024-02-29 9:26 ` Patrick Huesmann
2024-02-29 9:48 ` Alexander Kanavin [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='CANNYZj8fGE=pCNSTLD8VP+xsXBZA=MYtGM5jDdnn4eG1fSHrRw@mail.gmail.com' \
--to=alex.kanavin@gmail.com \
--cc=patrick.huesmann@desy.de \
--cc=yocto@lists.yoctoproject.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).