<davidlt[m]>
The builds get into the destination tags.
<davidlt[m]>
Build tag is only for the Koji.
<davidlt[m]>
Your packages will be built using chroot created from build tag repo.
<Entei[m]>
So how does koji where to get the SRPMs from ?
<davidlt[m]>
You tell it via koji build command
<Entei[m]>
* does koji know where to
<davidlt[m]>
Koji itself doesn't know.
<davidlt[m]>
It does have SCM filter rules that is all.
<Entei[m]>
davidlt[m]: I am not using any SCMs currently. Didn't put anything in allowed_scms
<davidlt[m]>
You can pass SRPM directly to Koji too.
<davidlt[m]>
But you loose ability to easily track your work.
<davidlt[m]>
Good for experiments and similar through.
<Entei[m]>
davidlt[m]: And yes this. I was thinking should that rpm repo be under the build tag instead, not under destination tag like what the article is getting to
<ol>
What do you guys think about it? Does it implement modern enough RISC-V?
zsun has quit [Quit: Leaving.]
zsun has joined #fedora-riscv
<Entei[m]>
<davidlt[m]> "There is significantly more..." <- yeah noticed it's basically the LicheePi4A, even less features and connectors actually. But the availability makes a big difference. Being available on Farnell and Digikey is huge plus in my dictionary.
<rwmjones>
davidlt[m]: meeting is in 1 hour I think?