Path: csiph.com!aioe.org!bofh.it!news.nic.it!robomod From: Stuart Prescott Newsgroups: linux.debian.maint.python Subject: Re: Updated PEP 394 (python and python2 commands) Date: Sat, 19 May 2018 07:30:01 +0200 Message-ID: References: X-Mailbox-Line: From debian-python-request@lists.debian.org Sat May 19 05:24:58 2018 Old-Return-Path: X-Amavis-Spam-Status: No, score=-5.957 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, HEADER_FROM_DIFFERENT_DOMAINS=0.25, LDO_WHITELIST=-5, RDNS_NONE=0.793] autolearn=no autolearn_force=no X-Policyd-Weight: using cached result; rate: -6.1 X-Injected-Via-Gmane: http://gmane.org/ Lines: 44 MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7Bit User-Agent: KNode/4.14.10 X-Mailing-List: archive/latest/15972 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/pdocac$6jb$1@blaine.gmane.org Approved: robomod@news.nic.it Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Date: Sat, 19 May 2018 15:24:29 +1000 X-Original-Message-ID: X-Original-References: <6dc7af52-174f-04c5-9149-cc5affa8afb1@debian.org> <20180518091951.jk6gvppn7yxyx5zp@sar0.p1otr.com> <2129b34f-a837-2d14-4400-3fa44785885d@debian.org> <20180518170216.pkxk44ipymh3jspv@sar0.p1otr.com> <20180518172417.kke4qgitz73uihog@sar0.p1otr.com> <38444031-1db5-6cda-f8c2-063580be7d30@debian.org> X-Original-X-Complaints-To: usenet@blaine.gmane.org Xref: csiph.com linux.debian.maint.python:10567 Matthias Klose wrote: > The distro should get > out of the way of using the python symlink, and giving users the freedom / > choice what to do about the link. I think I understand your rationale to stop shipping /usr/bin/python and once the unversioned symlink disappears from use in Debian then at least that particular avenue to breaking one's system disappears. What I don't understand is why any changes to package names or dependencies are required to achieve that goal. It sounds like a reasonable amount of work in your proposal, but once we no longer have any Python 2 applications left at some stage in the bullseye cycle, isn't the following sufficient? --- a/debian/rules +++ b/debian/rules @@ -247,12 +247,9 @@ binary-arch: build install stamp-doc : # provide the python and python.1 defaults mkdir -p debian/python-minimal/usr/bin - ln -sf python$(VER) debian/python-minimal/usr/bin/python ln -sf python$(VER) debian/python-minimal/usr/bin/python2 mkdir -p debian/python-minimal/usr/share/man/man1 - ln -sf python$(VER).1.gz \ - debian/python-minimal/usr/share/man/man1/python.1.gz ln -sf python$(VER).1.gz \ debian/python-minimal/usr/share/man/man1/python2.1.gz and then either later in the bullseye or bookworm cycles, those python- defaults simply go away along with all the other 'unversioned' python module and interpreter packages. What have I (and others!) missed that would make a rather elaborate packaging dance preferable to this? cheers Stuart -- Stuart Prescott http://www.nanonanonano.net/ stuart@nanonanonano.net Debian Developer http://www.debian.org/ stuart@debian.org GPG fingerprint 90E2 D2C1 AD14 6A1B 7EBB 891D BBC1 7EBB 1396 F2F7