From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751495AbcFBE15 (ORCPT ); Thu, 2 Jun 2016 00:27:57 -0400 Received: from know-smtprelay-omc-8.server.virginmedia.net ([80.0.253.72]:39471 "EHLO know-smtprelay-omc-8.server.virginmedia.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750854AbcFBE14 (ORCPT ); Thu, 2 Jun 2016 00:27:56 -0400 X-Greylist: delayed 501 seconds by postgrey-1.27 at vger.kernel.org; Thu, 02 Jun 2016 00:27:56 EDT X-Originating-IP: [81.100.29.190] X-Spam: 0 X-Authority: v=2.1 cv=dbJ9pije c=1 sm=1 tr=0 a=+He7s6SjlwGdCRwhjLOitA==:117 a=+He7s6SjlwGdCRwhjLOitA==:17 a=L9H7d07YOLsA:10 a=9cW_t1CCXrUA:10 a=s5jvgZ67dGcA:10 a=IkcTkHD0fZMA:10 a=pD_ry4oyNxEA:10 a=PNqkFi2N56eFX-4cYkwA:9 a=QEXdDO2ut3YA:10 Date: Thu, 2 Jun 2016 05:19:34 +0100 From: Ken Moffat To: Boris Rybalkin Cc: "Austin S. Hemmelgarn" , Nicolai Stange , linux-kernel@vger.kernel.org, Vladimir Sapronov Subject: Re: script relative shebang Message-ID: <20160602041934.GA13820@milliways.localdomain> References: <87lh2pj0gi.fsf@gmail.com> <1A095838-A4DA-4215-8AB7-6ACC92802F0D@gmail.com> <9d6adc59-3893-18f9-c003-c54a1db9e3cc@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline X-Clacks-Overhead: GNU Terry Pratchett Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.6.1 (2016-04-27) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Jun 02, 2016 at 01:04:46AM +0100, Boris Rybalkin wrote: > Sorry for insisting, but I would like to explore potential solutions > for fixing the root problem (missing relative shebang), > I know there are ways to workaround that, but I would like to make > sure the proper fix is not possible. > I understood that it is too late to introduce additional keywords > after #! as existing systems expect fs path there, OK. > But what about changing #! itself, is it possible to introduce another > special sequence like #? to denote a relative mode: > > #?python/bin/python > If you are able to get that accepted, it will only work on linux systems running such recent kernels. For your own systems, you can of course do whatever you wish. But for public availability you will then need to wait several years until your target linux users can be expected to have moved to a suitable kernel (presumably the *next* long-term stable kernel after the change is accepted : I guess that version is perhaps the best part of a year away even if your change got accepted into 4.8, and then you need your users' distros to move to it). To me, that doesn't seem worth the trouble (to you) of coding it, getting it reviewed and eventually accepted, and then fixing up whatever problems arise after it gets into linux-next [ problems will always appear, even if the new code turns out not to be the cause ]. And first, you have to persuade somebody influential that this is a good thing to do, particularly when people have suggested alternative approaches. I don't count, but at the moment I've not seen any good reasons why the kernel should be changed to support this. But it's your time, and your itch to scratch. ĸen -- I had to walk fifteen miles to school, barefoot in the snow. Uphill both ways.