Re: Strange covert module builds [sbergmann ?]

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

 



> That new thing then gets leveraged into the next new thing with multiple layers that would make MC Escher and Rube Goldberg proud.
Awesome :D ...

TL;DR:
I don't need to investigate it further.
I was afraid of rouge Fedora Module builds, which actually didn't happen.

If flatpack needs to rebuild everything for them again, it's a pity
(from the infrastructure load POV), but I'd guess there's no other way
currently.

Thanks for confirmation and clarification.

--

Michal Schorm
Software Engineer
Core Services - Databases Team
Red Hat

--

On Mon, Mar 2, 2020 at 2:05 PM Stephen John Smoogen <smooge@xxxxxxxxx> wrote:
>
>
>
> On Mon, 2 Mar 2020 at 07:32, Michal Schorm <mschorm@xxxxxxxxxx> wrote:
>>
>> Can you please brief me really quick on how does the flatpack work
>> from maintainer POV? (what does it need for build / creation; what
>> does it need for runtime )
>>
>> If the flatpack uses the packages from base Fedora;
>> 'rpms/mariadb-connector-c', which I'm the maintainer of probably sent
>> me the email to notify me, that someone somewhere built the package -
>> which would be expected.
>>
>> Anyway, that doesn't clarify to me why the builds looks so much like
>> module builds.
>>
>
> The build system usually has to leverage whatever currently works and is available to make whatever new thing people want to work. That new thing then gets leveraged into the next new thing with multiple layers that would make MC Escher and Rube Goldberg proud.
>
> I believe that Flatpacks use the container buildsystem which then relies on parts of the module build system and some other items to accomplish their tasks. How each of those deliver emails would depend on what tool emailed.. it might be the build system itself or it could be some part of the FMN (no idea what that stands for today) which saw a fedmsg which matched a filter you are marked to get.
>
>
> --
> Stephen J Smoogen.
>
> _______________________________________________
> 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




[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