When is Something Built from Source
-
@scottalanmiller said in When is Something Built from Source:
@DustinB3403 said in When is Something Built from Source:
So you're saying bash is a compiler?
No, BASH is an interpreter.
Right.
-
@Dashrender said in When is Something Built from Source:
@DustinB3403 said in When is Something Built from Source:
The end result is an installed application.
If you want to call them both installers - sure, I'd definitely agree with that. But one is compiled and one is not. Huge difference there.
Compilers are not installers. If you run Visual Basic and get an exe file, you still need to do the installation step. Compilation itself doesn't do the installing.
So we have two completely different things. With VB we compile but don't install. With the XO script we install but don't compile. They actually don't overlap at all.
-
@scottalanmiller said in When is Something Built from Source:
@DustinB3403 said in When is Something Built from Source:
@Dashrender said in When is Something Built from Source:
@DustinB3403 said in When is Something Built from Source:
So @scottalanmiller would you call https://github.com/Jarli01/xenorchestra_installer a "precompiled installer"?
I wouldn't, it's an installation script. There's nothing compiled about it.
Why wouldn't you? Think back to when I went through the process of installing XO into Ubuntu 14 (or whatever it was).
I then compressed the commands down, and @scottalanmiller wrote a script for it. That script pulls in everything you need to install XO.
This is similar to Visual Basic, except you don't have an .exe but a .sh file that does the job.
The end result is an installed application.
Because they aren't similar, at all. One is compiling, one is copying. In one case you start with a script and just move it between two different places, in the other you compile something and have something that can be executed.
Or to look at it another way....
Visual Basic you start with code and end up with an executable.
XO you start with code and end with code and an executable that was already on the system (NodeJS) runs that code. NodeJS is the executable, not XO.
To really push this further - XO is not an application - at least not in my eyes.. it's customization that runs on top of an application, that application being NodeJS.
-
@scottalanmiller said in When is Something Built from Source:
XO you start with code and end with code and an executable that was already on the system (NodeJS) runs that code. NodeJS is the executable, not XO.
Um... we install nodejs. It doesn't exist (or doesn't have too)
https://raw.githubusercontent.com/scottalanmiller/xenorchestra_installer/master/xo_install.sh
sudo apt-get install --yes nodejs
-
@Dashrender said in When is Something Built from Source:
@scottalanmiller said in When is Something Built from Source:
@DustinB3403 said in When is Something Built from Source:
@Dashrender said in When is Something Built from Source:
@DustinB3403 said in When is Something Built from Source:
So @scottalanmiller would you call https://github.com/Jarli01/xenorchestra_installer a "precompiled installer"?
I wouldn't, it's an installation script. There's nothing compiled about it.
Why wouldn't you? Think back to when I went through the process of installing XO into Ubuntu 14 (or whatever it was).
I then compressed the commands down, and @scottalanmiller wrote a script for it. That script pulls in everything you need to install XO.
This is similar to Visual Basic, except you don't have an .exe but a .sh file that does the job.
The end result is an installed application.
Because they aren't similar, at all. One is compiling, one is copying. In one case you start with a script and just move it between two different places, in the other you compile something and have something that can be executed.
Or to look at it another way....
Visual Basic you start with code and end up with an executable.
XO you start with code and end with code and an executable that was already on the system (NodeJS) runs that code. NodeJS is the executable, not XO.
To really push this further - XO is not an application - at least not in my eyes.. it's customization that runs on top of an application, that application being NodeJS.
It's an application, just not an executable
-
@scottalanmiller said in When is Something Built from Source:
@Dashrender said in When is Something Built from Source:
@DustinB3403 said in When is Something Built from Source:
The end result is an installed application.
If you want to call them both installers - sure, I'd definitely agree with that. But one is compiled and one is not. Huge difference there.
Compilers are not installers. If you run Visual Basic and get an exe file, you still need to do the installation step. Compilation itself doesn't do the installing.
So we have two completely different things. With VB we compile but don't install. With the XO script we install but don't compile. They actually don't overlap at all.
Oh that's not what I meant - but I see why you went there.
I was comparing his VB6 output (the .exe) to the .sh file. Those are both installers.
-
@DustinB3403 said in When is Something Built from Source:
Um... we install nodejs. It doesn't exist (or doesn't have too)
https://raw.githubusercontent.com/scottalanmiller/xenorchestra_installer/master/xo_install.sh
sudo apt-get install --yes nodejs
NodeJS is not part of XO. You are installing it first. Then installing XO. Then NodeJS is running.
If you want to say that NodeJS is precompiled, that's fine. But again, this is the same as XOA.
-
@scottalanmiller said in When is Something Built from Source:
@Dashrender said in When is Something Built from Source:
@scottalanmiller said in When is Something Built from Source:
@DustinB3403 said in When is Something Built from Source:
@Dashrender said in When is Something Built from Source:
@DustinB3403 said in When is Something Built from Source:
So @scottalanmiller would you call https://github.com/Jarli01/xenorchestra_installer a "precompiled installer"?
I wouldn't, it's an installation script. There's nothing compiled about it.
Why wouldn't you? Think back to when I went through the process of installing XO into Ubuntu 14 (or whatever it was).
I then compressed the commands down, and @scottalanmiller wrote a script for it. That script pulls in everything you need to install XO.
This is similar to Visual Basic, except you don't have an .exe but a .sh file that does the job.
The end result is an installed application.
Because they aren't similar, at all. One is compiling, one is copying. In one case you start with a script and just move it between two different places, in the other you compile something and have something that can be executed.
Or to look at it another way....
Visual Basic you start with code and end up with an executable.
XO you start with code and end with code and an executable that was already on the system (NodeJS) runs that code. NodeJS is the executable, not XO.
To really push this further - XO is not an application - at least not in my eyes.. it's customization that runs on top of an application, that application being NodeJS.
It's an application, just not an executable
New thread.
-
@Dashrender said in When is Something Built from Source:
I was comparing his VB6 output (the .exe) to the .sh file. Those are both installers.
To which .sh file? The .exe is NOT an installed. The script file of XO is not an installer either. But the .sh that we made to install it, is. VB does not create installers at all, unless you are writing your own.
-
@DustinB3403 said in When is Something Built from Source:
@scottalanmiller said in When is Something Built from Source:
XO you start with code and end with code and an executable that was already on the system (NodeJS) runs that code. NodeJS is the executable, not XO.
Um... we install nodejs. It doesn't exist (or doesn't have too)
https://raw.githubusercontent.com/scottalanmiller/xenorchestra_installer/master/xo_install.sh
sudo apt-get install --yes nodejs
ANd important to note, if the system already runs Node for anything, like if you had NodeBB on there, then the script does not install it, it just checked for it to be there.
-
@scottalanmiller said in When is Something Built from Source:
@Dashrender said in When is Something Built from Source:
I was comparing his VB6 output (the .exe) to the .sh file. Those are both installers.
To which .sh file? The .exe is NOT an installed. The script file of XO is not an installer either. But the .sh that we made to install it, is. VB does not create installers at all, unless you are writing your own.
Dustin said that he would install from the .exe he got from VB6 - so I was riding that wave.
@DustinB3403 said in When is Something Built from Source:
Think of Visual Basic, you write the code, design the form, and then you compile it, and get an executable that you can ship out and anyone can install the application from.
Then taking that wave, along with talking about the installer script that you and he made for XO, we now have two things that are both installers.
-
@Dashrender said in When is Something Built from Source:
@scottalanmiller said in When is Something Built from Source:
@Dashrender said in When is Something Built from Source:
I was comparing his VB6 output (the .exe) to the .sh file. Those are both installers.
To which .sh file? The .exe is NOT an installed. The script file of XO is not an installer either. But the .sh that we made to install it, is. VB does not create installers at all, unless you are writing your own.
Dustin said that he would install from the .exe he got from VB6 - so I was riding that wave.
You need to install it somewhere, but the exe itself isn't an installer, it is the thing to be installed.
-
@Dashrender said in When is Something Built from Source:
Then taking that wave, along with talking about the installer script that you and he made for XO, we now have two things that are both installers.
Right IF you made an installer for his VB6 application, then that would be comparable to the XO install script that we made. But the VB6 exe itself is comparable to the XO scripts themselves, the part being installed.
-
@DustinB3403 said in When is Something Built from Source:
@scottalanmiller said in When is Something Built from Source:
XO you start with code and end with code and an executable that was already on the system (NodeJS) runs that code. NodeJS is the executable, not XO.
Um... we install nodejs. It doesn't exist (or doesn't have too)
https://raw.githubusercontent.com/scottalanmiller/xenorchestra_installer/master/xo_install.sh
sudo apt-get install --yes nodejs
So do you assume that you're running some kind of compiler when you install Wireshark and it helps you out by installing WinPCap (another precompiled piece of software)?
-
@scottalanmiller said in When is Something Built from Source:
@Dashrender said in When is Something Built from Source:
Then taking that wave, along with talking about the installer script that you and he made for XO, we now have two things that are both installers.
Right IF you made an installer for his VB6 application, then that would be comparable to the XO install script that we made. But the VB6 exe itself is comparable to the XO scripts themselves, the part being installed.
Understood and agreed. See just more more order of confusion tossed on the pile.
-
@Dashrender said in When is Something Built from Source:
@scottalanmiller said in When is Something Built from Source:
@Dashrender said in When is Something Built from Source:
Then taking that wave, along with talking about the installer script that you and he made for XO, we now have two things that are both installers.
Right IF you made an installer for his VB6 application, then that would be comparable to the XO install script that we made. But the VB6 exe itself is comparable to the XO scripts themselves, the part being installed.
Understood and agreed. See just more more order of confusion tossed on the pile.
Shouldn't be. It's all about compilation or not.
-
@Dashrender said in When is Something Built from Source:
@DustinB3403 said in When is Something Built from Source:
@scottalanmiller said in When is Something Built from Source:
XO you start with code and end with code and an executable that was already on the system (NodeJS) runs that code. NodeJS is the executable, not XO.
Um... we install nodejs. It doesn't exist (or doesn't have too)
https://raw.githubusercontent.com/scottalanmiller/xenorchestra_installer/master/xo_install.sh
sudo apt-get install --yes nodejs
So do you assume that you're running some kind of compiler when you install Wireshark and it helps you out by installing WinPCap (another precompiled piece of software)?
Only if you (your .sh or exe) check to see if the item is there or not and required could you consider that even remotely. We're checking to see if a dependency is installed, if not we install the dependency.
-
@DustinB3403 said in When is Something Built from Source:
@Dashrender said in When is Something Built from Source:
@DustinB3403 said in When is Something Built from Source:
@scottalanmiller said in When is Something Built from Source:
XO you start with code and end with code and an executable that was already on the system (NodeJS) runs that code. NodeJS is the executable, not XO.
Um... we install nodejs. It doesn't exist (or doesn't have too)
https://raw.githubusercontent.com/scottalanmiller/xenorchestra_installer/master/xo_install.sh
sudo apt-get install --yes nodejs
So do you assume that you're running some kind of compiler when you install Wireshark and it helps you out by installing WinPCap (another precompiled piece of software)?
Only if you (your .sh or exe) check to see if the item is there or not and required could you consider that even remotely. We're checking to see if a dependency is installed, if not we install the dependency.
Only if? What about "checking to see if something is there" correlates with compilation? That's totally unrelated.
-
@scottalanmiller said in When is Something Built from Source:
@DustinB3403 said in When is Something Built from Source:
@Dashrender said in When is Something Built from Source:
@DustinB3403 said in When is Something Built from Source:
@scottalanmiller said in When is Something Built from Source:
XO you start with code and end with code and an executable that was already on the system (NodeJS) runs that code. NodeJS is the executable, not XO.
Um... we install nodejs. It doesn't exist (or doesn't have too)
https://raw.githubusercontent.com/scottalanmiller/xenorchestra_installer/master/xo_install.sh
sudo apt-get install --yes nodejs
So do you assume that you're running some kind of compiler when you install Wireshark and it helps you out by installing WinPCap (another precompiled piece of software)?
Only if you (your .sh or exe) check to see if the item is there or not and required could you consider that even remotely. We're checking to see if a dependency is installed, if not we install the dependency.
Only if? What about "checking to see if something is there" correlates with compilation? That's totally unrelated.
Lets take any horrid windows installer. It might check to see if .Net is installed, if not it prompts you to go an download .Net and then install .Net
Once .Net is installed, you try the installation again, this time it passes all checks.
My point is, we are checking for dependencies, and then pulling in anything required automatically.
-
@DustinB3403 said in When is Something Built from Source:
@scottalanmiller said in When is Something Built from Source:
@DustinB3403 said in When is Something Built from Source:
@Dashrender said in When is Something Built from Source:
@DustinB3403 said in When is Something Built from Source:
@scottalanmiller said in When is Something Built from Source:
XO you start with code and end with code and an executable that was already on the system (NodeJS) runs that code. NodeJS is the executable, not XO.
Um... we install nodejs. It doesn't exist (or doesn't have too)
https://raw.githubusercontent.com/scottalanmiller/xenorchestra_installer/master/xo_install.sh
sudo apt-get install --yes nodejs
So do you assume that you're running some kind of compiler when you install Wireshark and it helps you out by installing WinPCap (another precompiled piece of software)?
Only if you (your .sh or exe) check to see if the item is there or not and required could you consider that even remotely. We're checking to see if a dependency is installed, if not we install the dependency.
Only if? What about "checking to see if something is there" correlates with compilation? That's totally unrelated.
Lets take any horrid windows installer. It might check to see if .Net is installed, if not it prompts you to go an download .Net and then install .Net
Once .Net is installed, you try the installation again, this time it passes all checks.
My point is, we are checking for dependencies, and then pulling in anything required automatically.
Okay, but none of those pieces are in any way related to compilation.
