cederom commented on issue #8580: URL: https://github.com/apache/nuttx/issues/8580#issuecomment-1437755648
* I think that simple `SED_CMD` in the top level config selected by `tools/configure.sh` will do the job.. just a lot of work to update all `sed` with `SED_CMD`, I hope to find some free moment for this soon :-P * This long line issue may be rewritten somehow so it works on BSD `sed`, but it may also reflect some bug in the bsd implementation. * FreeBSD is organized around "base system" located at `/` that is always common and non alterable (it can be loaded from a standard hard drive but also ROM like image of BOOTP/NFS share), and the "userland" located at `/usr/local` (that can be also loaded from a local hard drive but also another NFS share). All user related configurations and applications can only reside under `/usr/local`. The `/` part is nonalterable (maybe except `/etc`, `/var`, `/tmp` etc). This is why I cannot (don't want to) touch anything in `/bin` or `/usr/bin` because that would make my system non-compatible with the other standard FreeBSD installations. This may look a bit stiff, but this keeps the environment clean, known, and coherent for all FreeBSD installations wherever it is installed and whenever it was installed (i.e. 10 years ago or 20 years ago it was exactly the same). This is why I prefer BSD Unix over Linux. * Using GNU Sed everywhere will result in reproducible results. Even on systems that have their own `sed` implementation (like BSD). I know this is quite trivial but I have some dozens urgent tasks right now. I would really dream of having more time to play with NuttX please forgive me. When I do the fix I will for sure send a PR :-) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@nuttx.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
