Timeline for Build system for shell scripts
Current License: CC BY-SA 3.0
13 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 12, 2015 at 22:36 | comment | added | Mark Plotnick |
May want to look at m4, which is used to create customized autoconf shell scripts. gnu.org/software/autoconf/manual/…
|
|
| Jan 9, 2015 at 18:15 | answer | added | dataless | timeline score: 0 | |
| Jan 9, 2015 at 15:48 | comment | added | Avindra Goolcharan | And inlining arbitrary code into one master script is much "scarier," but that's hard to explain to people who don't know any better. | |
| Jan 9, 2015 at 15:45 | comment | added | Chris Down | If you are willing to build a convoluted system to do this, but are not willing to consider the (long solved, and far more sustainable) solution of shipping more than 1 file in your deployment, I think you're headed down the wrong path. Good luck though. :-) | |
| Jan 9, 2015 at 15:44 | comment | added | Avindra Goolcharan | Sure, but then you would have to deploy >= 2 files per server. It's doable but that is not the point of my question. | |
| Jan 9, 2015 at 15:41 | comment | added | Chris Down | ...which seems the far preferable solution. | |
| Jan 9, 2015 at 15:41 | comment | added | Avindra Goolcharan | The point of the build system would be to inline the Python code. Otherwise I would just create multiple scripts and link them together with pipes and environment variables. | |
| Jan 9, 2015 at 15:38 | comment | added | Chris Down | You have not read my reply correctly, I am not suggesting that you should make your wrapper a Python script. I am suggesting that you do not inline Python code. | |
| Jan 9, 2015 at 15:37 | comment | added | Avindra Goolcharan |
The tool MUST modify environment variables in the calling / source / parent shell, which can only be done by calling . script.sh. Therefore, the wrapper script CANNOT be a python script.
|
|
| Jan 9, 2015 at 15:36 | comment | added | Chris Down | Why inline the code at all? That seems like a strange thing to do. It would likely be better to have clear separation between your Python code and your shell script. | |
| Jan 9, 2015 at 15:35 | comment | added | Avindra Goolcharan | Let me try to make this simpler. I have a script wrapper.sh, which references stuff.py. I want to say "build" and the build tool inlines the python code in a call as described in my post. The end result should be a 'program.sh' with all code inlined. | |
| Jan 9, 2015 at 15:31 | comment | added | Chris Down | I really don't understand what you are asking here, or what you want to happen. What is your question, specified as succinctly as possible? | |
| Jan 9, 2015 at 15:24 | history | asked | Avindra Goolcharan | CC BY-SA 3.0 |