----- Original Message ----- > From: "Randy Barlow" <bowlofeggs@xxxxxxxxxxxxxxxxx> > To: "Development discussions related to Fedora" <devel@xxxxxxxxxxxxxxxxxxxxxxx> > Sent: Thursday, October 17, 2019 1:18:08 PM > Subject: Re: Fedora 32 System-Wide Change proposal: Modules in Non-Modular Buildroot > > On Thu, 2019-10-17 at 12:56 -0400, Randy Barlow wrote: > > I > > had to write a yaml file that listed hashes of every dependency of > > rpick, and every dependency of those dependencies, and their > > dependencies, and so on. > > By the way, I didn't actually end up doing this, Igor did it for me. I > didn't mean to take credit, I mean more that "I, the packager, had to > do this", not "I, Randy, had to do this". Igor rocks. Just for the obvious reply... :) `ref` behaves just like `git checkout` would. So yeah, you can pass a very explicit hash and then you won't get any updates until you bump the hash in the spec again. However, you could pass tags (like you mention in the comment next to each hash) or branches instead. The latter is what some other modules do, like the eclipse one: https://src.fedoraproject.org/modules/eclipse/blob/2019-06/f/eclipse.yaml#_1069 See also: https://github.com/fedora-modularity/libmodulemd/blob/master/spec.v2.yaml#L268-L273 In the latter case (in RHEL at least), you have to commit a (potentially empty) commit to the module and then a rebuild of the module will pull in the latest contents from the branches you specify for each component RPM. Perhaps we need to collect a "tips and tricks" section for modularity? HTH, Alex > > _______________________________________________ > devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx > _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
