Path: csiph.com!aioe.org!bofh.it!news.nic.it!robomod From: =?UTF-8?B?Tmd1eeG7hW4gSOG7k25nIFF1w6Ju?= Newsgroups: linux.debian.maint.python Subject: Re: Backport of Python 3.6 for Debian Stretch? Date: Tue, 24 Apr 2018 18:50:01 +0200 Message-ID: References: X-Mailbox-Line: From debian-python-request@lists.debian.org Tue Apr 24 16:42:48 2018 Old-Return-Path: X-Amavis-Spam-Status: No, score=-1.12 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, EMPTY_BODY=3, FREEMAIL_FROM=0.001, FROM_EXCESS_BASE64=0.979, HTML_MESSAGE=2, LDO_WHITELIST=-5, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=no autolearn_force=no X-Policyd-Weight: using cached result; rate: -7 Dkim-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=NZSq868X7E4KQg1JOk62rdw2Rn/RID/aLvdQ+F2w/T0=; b=Wx9N2UFnbo4/7WeuCJlN8XjMsXo7XjIklIGp/tmxLbNnLqjH4sd0lX0CVbidLDtYXJ BZwiMN4BygCez/0VNmFfwklTD5XN3wfNgwzmPMJIux5ZbtOHmoFi18e0z9Nk1uVLSzRV h2tjOHAfvS7xYGnYSk5Z1MTskQ9cY8nfHpL0Zl3l2YeOb1aYpn+jZHvMsDCm/uDfVbMz EtTfpukrHGu7bm3dPyxTgAT2xX1cSJ0TjZIK0OZVKhNJBO4CwY1jKgf2AJjyeIKFw3ph o1tE16iAqBoTfUys6s/sy1QLm2C1MD6PoRv0HcvNf9xv/wlqtLSEmLvNTDOIFbwjVT+L aokA== X-Google-Dkim-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=NZSq868X7E4KQg1JOk62rdw2Rn/RID/aLvdQ+F2w/T0=; b=WHnjiV3D7PcgURQFXWpiza5AHMODCfWncYb5Kv+HRsGPSQsNHGJVLQKlShy/9bdeey 3I9t2n+3/SroNMuibxSoXUm7dW3p9VQpA3/mNbF2lQ6Mdy9NcvM4RHGNoAz8x5HsS3F4 vItl7NsPy5lHUAR9FcoLm3xsTO8VPQeaob2Fv19wuqylByc0mVyUxuSMs1fg49XYc/BY VJZjApK23ONX6Zwgn62pvZm74Jvy3PfrDATHDQ68dnyDXfE5W56OxhvQk3t5XmU1T0gB kGb4YbCvecBAiaBdJk0EUowBXJpd38SP4GwE6mx0gUCSC4BgabK7muPMxxpmX7EY0eNA h08A== X-Gm-Message-State: ALQs6tAQqZ+ihhfbsgkaTgUPcvgvtRT3Dz/V34XFLegKDAAjP7vF26tE Mcm8S/jqNs0lRphjkOYC96yWFrux/GcHVP07/Mk= X-Google-SMTP-Source: AB8JxZrLjql361iANLBRHKs/UC+3p5yS4AL7FayJ8E+nDLz7dVPYIgHMyrTQofBkGExqGxauvt+0MqmuOkR0ANAQSc8= X-Received: by 10.12.173.251 with SMTP id x56mr4802967qvc.198.1524588150630; Tue, 24 Apr 2018 09:42:30 -0700 (PDT) MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="001a1143255a25aeba056a9ad7a0" X-Mailing-List: archive/latest/15856 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/CAL-RyxjEtt_MRGHfbXWXLJ=iOqhTVetEaYebh55UANPXn=MxZw@mail.gmail.com Approved: robomod@news.nic.it Lines: 98 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Cc: debian-python X-Original-Date: Tue, 24 Apr 2018 23:42:30 +0700 X-Original-Message-ID: X-Original-References: <20180424151917.jxgx3n23n3uc76w7@yuggoth.org> Xref: csiph.com linux.debian.maint.python:10455 --001a1143255a25aeba056a9ad7a0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Tue, Apr 24, 2018 at 10:19 PM, Jeremy Stanley wrote: > On 2018-04-24 22:07:03 +0700 (+0700), Nguy=E1=BB=85n H=E1=BB=93ng Qu=C3= =A2n wrote: > [...] > > I don't need to "not disturb" system. > > If have to use conda, pyenv, I would rather build Python3.6 from source > > tarball, not to bring more overhead (conda body, pyenv body), and > > "Python3.6 from source" still not disturb my system, because it is > > installed to "/usr/local". > > > > But I don't want any method that requires to build Python from source > > (tarball, pythonz, conda or alike), because I really need *pre-built > > binaries*. > [...] > > Unless I'm missing something, there's no substantial difference > between building a package of Python3.6 and copying it to the > system, or performing a `make altinstall` and copying the resulting > files (via rsync, tar and scp, whatever) to the target system. If > you're okay with the idea of building packages remotely, then why > not build from source remotely? > =E2=80=8BThen why Debian project invent *.deb file, not just pack binary as= tar file and let user to untar it?=E2=80=8B =E2=80=8BI favor building deb file, rather than copying "make altinstall" r= esult, because of the same reason.=E2=80=8B --=20 Qu=C3=A2n Nguy=E1=BB=85n H=E1=BB=93ng Qu=C3=A2n =E2=98=8E 093 9030 338 Facebook: ng.hong.quan =F0=9F=8C=8F quan.hoabinh.vn agriconnect.vn --001a1143255a25aeba056a9ad7a0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

<= /div>

On Tue, Apr = 24, 2018 at 10:19 PM, Jeremy Stanley <fungi@yuggoth.org> wro= te:
On 2018-04-24 22:07:03 +0700 (+0700),= Nguy=E1=BB=85n H=E1=BB=93ng Qu=C3=A2n wrote:
[...]
> I don't need to "not disturb" system. > If have to use conda, pyenv, I would rather build Python3.6 from sourc= e
> tarball, not to bring more overhead (conda body, pyenv body), and
> "Python3.6 from source" still not disturb my system, because= it is
> installed to "/usr/local".
>
> But I don't want any method that requires to build Python from sou= rce
> (tarball, pythonz, conda or alike), because I really need *pre-built > binaries*.
[...]

Unless I'm missing something, there's no substantial difference
between building a package of Python3.6 and copying it to the
system, or performing a `make altinstall` and copying the resulting
files (via rsync, tar and scp, whatever) to the target system. If
you're okay with the idea of building packages remotely, then why
not build from source remotely?

=E2=80=8BThen why Debian project = invent *.deb file, not just pack binary as tar file and let user to untar i= t?=E2=80=8B
=E2=80=8BI favor building deb file, rather than copying "make altinst= all" result, because of the same reason.=E2=80=8B


--
Qu=C3=A2n

Ng= uy=E1=BB=85n H=E1=BB=93ng Qu=C3=A2n
=E2=98=8E 093 9030 338
Facebook: = ng.hong.quan
=F0=9F=8C=8F = quan.hoabinh.vn=C2=A0 agriconnect.vn

--001a1143255a25aeba056a9ad7a0--