Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1412599
| From | Boris <ribalkin@gmail.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: script relative shebang |
| Date | 2016-06-03 00:50 +0200 |
| Message-ID | <rFJB8-3vM-27@gated-at.bofh.it> (permalink) |
| References | (1 earlier) <rF0Xo-s6-13@gated-at.bofh.it> <rF9nY-5Ug-39@gated-at.bofh.it> <rFgps-1H0-7@gated-at.bofh.it> <rFomZ-79H-11@gated-at.bofh.it> <rFsqC-1dm-13@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
I still think it is a good thing to do. I will try to implement it on github and may be some day someone influential will help me with that :) On 2 June 2016 05:19:34 BST, Ken Moffat <zarniwhoop@ntlworld.com> wrote: >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 -- Sent from my Android device with K-9 Mail. Please excuse my brevity.
Back to linux.kernel | Previous | Next — Previous in thread | Find similar | Unroll thread
script relative shebang Boris Rybalkin <ribalkin@gmail.com> - 2016-05-31 23:50 +0200
Re: script relative shebang Nicolai Stange <nicstange@gmail.com> - 2016-06-01 01:10 +0200
Re: script relative shebang Boris <ribalkin@gmail.com> - 2016-06-01 10:10 +0200
Re: script relative shebang Bernd Petrovitsch <bernd@petrovitsch.priv.at> - 2016-06-01 15:20 +0200
Re: script relative shebang "Austin S. Hemmelgarn" <ahferroin7@gmail.com> - 2016-06-01 17:40 +0200
Re: script relative shebang Boris Rybalkin <ribalkin@gmail.com> - 2016-06-02 02:10 +0200
Re: script relative shebang Ken Moffat <zarniwhoop@ntlworld.com> - 2016-06-02 06:30 +0200
Re: script relative shebang Boris <ribalkin@gmail.com> - 2016-06-03 00:50 +0200
csiph-web