Re: Is dist-git a good place for work?

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

 



On Thu, 7 May 2020 at 06:54, clime <clime@xxxxxxxxxxxxxxxxx> wrote:
>
> Dne čt 7. kvě 2020 12:19 uživatel Vít Ondruch <vondruch@xxxxxxxxxx> napsal:
>>
>>
>> Dne 06. 05. 20 v 20:39 clime napsal(a):
>> > On Wed, 6 May 2020 at 13:21, Fabio Valentini <decathorpe@xxxxxxxxx> wrote:
>> >> On Wed, May 6, 2020 at 10:37 AM Vít Ondruch <vondruch@xxxxxxxxxx> wrote:
>> >>>
>> >>> Dne 05. 05. 20 v 18:37 Fabio Valentini napsal(a):
>> >>>> On Mon, May 4, 2020 at 5:06 PM Tomas Tomecek <ttomecek@xxxxxxxxxx> wrote:
>> >>>>

>> You still need to have tarballs for SRPM. Therefore the exploded sources
>>
>> actually consumes more space, because you still have tarballs and on top
>> of that you have git repo.
>
>
> Can the tarballs for srpms be generated dynamically in build system from the exploded sources?
>

If there is one thing I have learned from our build system, anything
is possible with enough time, manpower and duct-tape. Just realize
that once it is built there will be a dozens of extra features needed
to debug all the transient problems that come from it. Also realize
that it will NEVER get removed from the system because some other
parts will be glued on top which needed one little thing from it.

A program will need a lot of debugging to deal with a lot of transient
errors which happen because we do a lot of builds. The heavy hitter on
using the builders are MBS and koschei which both be building
transient packages all the time. I expect it will find various things
where the build mostly worked but

a) the checkout partially failed..
b) there was a permission problem
c) the builder ran out of memory/disk space/something else
d) fill in a hundred different transient ghosts we run into regularly
with our current rube goldberg build system.

That will need various levels of debugging to figure out why it didn't
work and it would need staff to track down and fix it.


-- 
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




[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