Re: [modularity] Recommended platform: [] and version 2 format

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Thanks for explaining about it!
I found the part of "platform: []" in the document you shared.
https://docs.fedoraproject.org/en-US/modularity/making-modules/defining-modules/#_modular_dependencies

Jun


On Wed, Sep 12, 2018 at 11:07 AM, Adam Samalik <asamalik@xxxxxxxxxx> wrote:
> That's right!
>
> This and more is documented in the Modularity section of Fedora Docs:
> https://docs.fedoraproject.org/en-US/modularity/making-modules/defining-modules/
>
> On Wed, Sep 12, 2018 at 10:56 AM Jun Aruga <jaruga@xxxxxxxxxx> wrote:
>>
>> Just sharing information.
>>
>> When talking with a person in modularity team, I have told that for a
>> module config yaml file's below elements, the empty array "[]" was
>> recommended on Fedora.
>>
>> /data/dependencies/buildrequires/platform
>> /data/dependencies/requires/platform
>>
>> Because when platform is  "[]", the module is built on current
>> supported platforms (right now f28, f29, and f30). The binary of the
>> module are prepared for each platform.
>> I hope the document is updated including this recommended setting as a
>> best practice.
>>
>> ```
>> diff --git a/ruby.yaml b/ruby.yaml
>>          tracker: https://bugs.ruby-lang.org/
>>      dependencies:
>>          - buildrequires:
>> -            platform: [f29]
>> +            platform: []
>>            requires:
>> -            platform: [f29]
>> +            platform: []
>>      components:
>>          # SRPMs
>>          rpms:
>> ```
>>
>> Also seeing several modules' config YAML files, some config files are
>> still version 1.
>> I like to share that we can use the version 2, changing the /version
>> element from 1 to 2.
>>
>> Version 2 spec:
>> https://github.com/fedora-modularity/libmodulemd/blob/master/spec.v2.yaml
>>
>> Regards,
>>
>> --
>> Jun Aruga jaruga@xxxxxxxxxx
>> _______________________________________________
>> devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
>> To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
>> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
>> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>> List Archives:
>> https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
>
>
>
> --
>
> Adam Šamalík
> ---------------------------
> Software Engineer
> Red Hat
>
> _______________________________________________
> devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
> To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
>



-- 
Jun Aruga jaruga@xxxxxxxxxx
IRC: jaruga, Office: TPB(Technology Park Brno) Building C 1F, Brno,
Czech Republic
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux