Mailinglist Archive: opensuse-packaging (104 mails)

< Previous Next >
Re: [opensuse-packaging] Re: Splitting up binary packages for large SDKs
On 8/7/18 5:52 PM, Andreas Schwab wrote:
On Aug 07 2018, John Paul Adrian Glaubitz <adrian.glaubitz@xxxxxxxx> wrote:

Go even default to static linking by default.

Yes, that's a very silly thing to do.

As usual general statements like the above can be easily proven to be wrong by a counter example:

In automated container deployments you won't do any updates. You deliver an update of your service in a newly built container anyway (at least every two weeks or so). The advantage of having one statically linked binary is that you have a defined run-time environment delivered to production without all dependency hell on normal systems. Same reason why people use Python virtual envs or build everything into Java WARs. Of course you must have a decent CI/CD pipeline in place to make that a real advantage. And everything has pros and cons.

Note: The above is not meant as statement about how to
package libs in openSUSE.

Ciao, Michael.

< Previous Next >
Follow Ups