<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 05/20/2016 08:48 AM, Dean Troyer
wrote:<br>
</div>
<blockquote
cite="mid:CAOJFoEtuvOY-kjgojPscrcemqscK04e_6c5qitLNFsiYmvoqYg@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">On Fri, May 20, 2016 at 5:42 AM,
Thomas Goirand <span dir="ltr"><<a
moz-do-not-send="true" href="mailto:zigo@debian.org"
target="_blank"><a class="moz-txt-link-abbreviated" href="mailto:zigo@debian.org">zigo@debian.org</a></a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">I
am *NOT* buying that doing static linking is a progress.
We're back 30<br>
years in the past, before the .so format. It is amazing
that some of us<br>
think it's better. It simply isn't. It's a huge
regression, for package<br>
maintainers, system admins, production/ops, and our final
users. The<br>
only group of people who like it are developers, because
they just don't<br>
need to care about shared library API/ABI
incompatibilities and<br>
regressions anymore.<br>
</blockquote>
<div><br>
</div>
<div>I disagree, there are certainly places static linking
is appropriate, however, I didn't mention that at all.
Much of the burden with Python dependency at install/run
time is due to NO linking. Even with C, you make choices
at build time WRT what you link against, either statically
or dynamically. Even with shared libs, when the interface
changes you have to re-link everything that uses that
interface. It is not as black and white as you suggest.</div>
<div><br>
</div>
<div>And I say that as a user, who so desperately wants an
install process for OSC to match PuTTY on Windows: 1) copy
an .exe; 2) run it.</div>
<div>
<div class="gmail_quote"><br class="">
dt</div>
</div>
<div><br>
</div>
<div>[Thomas, I have done _EVERY_ one of the jobs above that
you listed, as a $DAY_JOB, and know exactly what it takes
to run production-scale services built from everything
from vendor packages to house-built source. It would be
nice if you refined your argument to stop leaning on
static linking as the biggest problem since stack
overflows. There are other reasons this might be a bad
idea, but I sense that you are losing traction fixating on
only this one.]</div>
</div>
</div>
</div>
</blockquote>
<br>
Static linking Bad. We can debate why elsewhere.<br>
<br>
Go with dynamic linking is possible, and should be what the
distributions target. This is a solvable problem.<br>
<br>
/me burns bikeshed and installs a Hubcycle/Citibike kiosk.<br>
<br>
<br>
<blockquote
cite="mid:CAOJFoEtuvOY-kjgojPscrcemqscK04e_6c5qitLNFsiYmvoqYg@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">
<div><br>
</div>
</div>
-- <br>
<div class="gmail_signature"><br>
Dean Troyer<br>
<a moz-do-not-send="true" href="mailto:dtroyer@gmail.com"
target="_blank">dtroyer@gmail.com</a><br>
</div>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: <a class="moz-txt-link-abbreviated" href="mailto:OpenStack-dev-request@lists.openstack.org?subject:unsubscribe">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a>
<a class="moz-txt-link-freetext" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a>
</pre>
</blockquote>
<br>
</body>
</html>