[OpenIndiana-discuss] gdb debugger
Till Wegmüller
toasterson at gmail.com
Fri Nov 14 21:39:16 UTC 2025
On 11/14/25 21:20, Andreas Wacknitz via openindiana-discuss wrote:
> Am 14.11.25 um 21:02 schrieb Toomas Soome via openindiana-discuss:
>>
>>> On 14. Nov 2025, at 19:15, Andreas Wacknitz via openindiana-discuss
>>> <openindiana-discuss at openindiana.org> wrote:
>>>
>>> Am 14.11.25 um 17:59 schrieb Reginald Beardsley via openindiana-discuss:
>>>> How much do the additional resources cost? I'm in for $100/
>>>> month. I can up that. It's my sole charity.
>>> Alas it's not only our servers (disk usage is usually between 30 and
>>> 60GB when I clean up the repo).
>>> The more important thing in this case is every client installation.
>>> IPS is using a SAT solver in order to determine what to do (eg.
>>> solving dependencies). With a growing number of package revisions
>>> memory consumption and calculation time grow non-linear. So the
>>> cleanup mainly happens to get these numbers down.
>>> This is one of the negative aspects of our rolling release model.
>>> With real releases you gain separate repositories and thus limit the
>>> number of package revisions.
>>>
>> Thats the curse of rolling updates; you “need” to keep available all
>> repo updates to make all those people with ancient setups happy;)
>> well, rolling release in fact means, you need to update often.
>> (considering the security, you should update often anyhow, but thats
>> another topic)
>>
>> My personal opinion is that rolling updates is bad not only because of
>> the issues about repositories but also because you will lose the
>> ability to have development/beta/.. releases and that means you will
>> start to be afraid of making mistakes and that means the end of
>> innovation.
>>
>> rgds,
>> toomas
>>
> I have tried to convince other contributors to discuss and plan to
> change to a release model.
> Nobody was willing to do so. I don't intend to do that alone.
>
> Andreas
I am onboard with a multi branch model but in the end we do end up too
little benefit to the development process. The breaking changes we would
prevent are only experienced by developers and the update issue stays.
We could grandfather out consolidations but that needs me having the
time to finish a POC for that. Which is on a low priority ATM.
-Till
>
> _______________________________________________
> openindiana-discuss mailing list
> openindiana-discuss at openindiana.org
> https://openindiana.org/mailman/listinfo/openindiana-discuss
More information about the openindiana-discuss
mailing list