| gnu_srs | Hello, now it's time to reveal I've created a patched sysvinit not depending on hardcoded paths: anybody interested? | 00:46 |
|---|---|---|
| onefang | Standalone and statically linked you mean? | 00:47 |
| gnu_srs | Moreover with some additional symlinks you can be independent of usrmerge (for that package). | 00:49 |
| gnu_srs | And, why are most scripts/code for sysvinit in debian/? | 00:50 |
| * onefang wonders if your sysvinit can handle my Lua based init script. | 00:51 | |
| onefang | You can write sysvinit scripts in any language. I've written them in C to. | 00:51 |
| gnu_srs | onefang: WDYM: I mean patches not using "/bin/file" instead using command -v "file" | 00:54 |
| gnu_srs | onefang: I don't follow you here? | 00:55 |
| gnu_srs | I'm talking about the sysvinit package, currently 3.13-1 | 00:56 |
| onefang | You said not depending on hardcoded paths, if the init script is written in Lua then it has to find Lua. If it's written in C, it might have to find it's libraries. But looks like you are just figuring out the paths on the fly, and shouldn't have an issue with that. | 00:56 |
| onefang | I'm talking about the scripts it runs. | 00:57 |
| gnu_srs | onefang: no its more like s//bin/pidof/`command -v pidof`/g | 01:03 |
| onefang | So long as you don't break my Lua based init script, I wont be annoyed at you. B-) | 01:04 |
| gnu_srs | I'm not interested in Lua, sorry :( | 01:07 |
| onefang | The point I was making is that init scripts CAN be written in any language. Sure 99.9% of them are some shell script variant, but sometimes some other language slips in. So keep that in mind when messing with it. You don't have to deal with Lua specifically, that's just a known example. | 01:08 |
| gnu_srs | I don't plan to mess with any other script language than shell scripts for now!? | 01:11 |
| onefang | That version of sysvinit you are patching already does. Don't break that is all I'm asking. | 01:11 |
| rrq | gnu_srs: my package sysvinit=3.06-4devuan3 only has the file "/usr/share/doc/sysvinit/copyright" .. you must mean another package | 01:16 |
| rrq | initscripts perhaps | 01:19 |
| plasma41 | gnu_srs: I think you'll find 's|/bin/pidof|`command -v pidof`|g' works better | 01:40 |
| plasma41 | gnu_srs: What PATH does sysvinit use? | 01:41 |
| rrq | another approach is to have an explicit PATH assignment at top and then use program names without path | 01:42 |
| rrq | though I don't have any involvement in devuan's fork(s) of these pacakages | 01:44 |
| gnu_srs | rrq: The patches are a mixture of PATH and command -v. And the changes are plenty! | 10:47 |
| gnu_srs | plasma41: I was trying to give an example of s/a/b/g not using that to replace hardcoded paths. | 10:48 |
| gnu_srs | Replacing hardcoded paths requires some attention, and that was used. | 10:49 |
| gnu_srs | Nevertheless why are almost all scripts under debian/ instead of in the upstream source code?? | 10:50 |
| gnu_srs | onefang: I did not break anything with the patched sysvinit! | 10:51 |
| plasma41 | gnu_srs: link to the patched sysvinit? | 21:18 |
| gnu_srs1 | I can email the patches for 3.13-1 | 21:47 |
| gnu_srs1 | Is devuan-dev OK? | 22:06 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!