__Falcon-Games__ wrote:

It's the Noml 0.3 release date today…

DifferentDance8 wrote:

__Falcon-Games__ wrote:

It's the Noml 0.3 release date today…

So does that mean Noml 0.3 is going to release?

__Falcon-Games__ wrote:

DifferentDance8 wrote:

__Falcon-Games__ wrote:

It's the Noml 0.3 release date today…

So does that mean Noml 0.3 is going to release?

Well I was going to release Pulanger today so Noml 0.3 is likely going to be pushed back, I am not sure how we can implement all of the features in ONE DAY. I only did a bit of work on pages.

DifferentDance8 wrote:

__Falcon-Games__ wrote:

DifferentDance8 wrote:

__Falcon-Games__ wrote:

It's the Noml 0.3 release date today…

So does that mean Noml 0.3 is going to release?

Well I was going to release Pulanger today so Noml 0.3 is likely going to be pushed back, I am not sure how we can implement all of the features in ONE DAY. I only did a bit of work on pages.

What the everloving frick even is Pulanger?

MagicCrayon9342 wrote:

For Linux and MacOS, a Makefile would be more suitable.

__Falcon-Games__ wrote:

MagicCrayon9342 wrote:

For Linux and MacOS, a Makefile would be more suitable.

It's written in Python. Also how in the world did you find this topic?

#!/usr/bin/env python3

make install

MagicCrayon9342 wrote:

__Falcon-Games__ wrote:

MagicCrayon9342 wrote:

For Linux and MacOS, a Makefile would be more suitable.

It's written in Python. Also how in the world did you find this topic?

It has nothing to do with what the program is written in, a Makefile is for compilation, installation, and uninstallation of programs. You can add

#!/usr/bin/env python3

to the top of the file, make it executable, and put it in /usr/bin (or I believe /usr/local/bin on MacOS) and it can simply be ran from any terminal no matter the current working directory. Do this with the make file, so that the user (if on Linux or MacOS) can simply run

make install

and the program will be installed. No need for installing additional dependencies just for the installer. I also recommend compiling the code to a single binary so that all dependencies are bundled instead of needing to be installed.

MagicCrayon9342 wrote:

__Falcon-Games__ wrote:

MagicCrayon9342 wrote:

For Linux and MacOS, a Makefile would be more suitable.

It's written in Python. Also how in the world did you find this topic?

It has nothing to do with what the program is written in, a Makefile is for compilation, installation, and uninstallation of programs. You can add

#!/usr/bin/env python3

to the top of the file, make it executable, and put it in /usr/bin (or I believe /usr/local/bin on MacOS) and it can simply be ran from any terminal no matter the current working directory. Do this with the make file, so that the user (if on Linux or MacOS) can simply run

make install

and the program will be installed. No need for installing additional dependencies just for the installer. I also recommend compiling the code to a single binary so that all dependencies are bundled instead of needing to be installed.

ajskateboarder wrote:

MagicCrayon9342 wrote:

__Falcon-Games__ wrote:

MagicCrayon9342 wrote:

For Linux and MacOS, a Makefile would be more suitable.

It's written in Python. Also how in the world did you find this topic?

It has nothing to do with what the program is written in, a Makefile is for compilation, installation, and uninstallation of programs. You can add

#!/usr/bin/env python3

to the top of the file, make it executable, and put it in /usr/bin (or I believe /usr/local/bin on MacOS) and it can simply be ran from any terminal no matter the current working directory. Do this with the make file, so that the user (if on Linux or MacOS) can simply run

make install

and the program will be installed. No need for installing additional dependencies just for the installer. I also recommend compiling the code to a single binary so that all dependencies are bundled instead of needing to be installed.

You would need GNU Make for that, which is not necessarily easy to install compared to just running a Python script

MagicCrayon9342 wrote:

ajskateboarder wrote:

MagicCrayon9342 wrote:

__Falcon-Games__ wrote:

MagicCrayon9342 wrote:

For Linux and MacOS, a Makefile would be more suitable.

It's written in Python. Also how in the world did you find this topic?

It has nothing to do with what the program is written in, a Makefile is for compilation, installation, and uninstallation of programs. You can add

#!/usr/bin/env python3

to the top of the file, make it executable, and put it in /usr/bin (or I believe /usr/local/bin on MacOS) and it can simply be ran from any terminal no matter the current working directory. Do this with the make file, so that the user (if on Linux or MacOS) can simply run

make install

and the program will be installed. No need for installing additional dependencies just for the installer. I also recommend compiling the code to a single binary so that all dependencies are bundled instead of needing to be installed.

You would need GNU Make for that, which is not necessarily easy to install compared to just running a Python script

Most distributions do one of two things:
1. Have it preinstalled
2. Have it in the repositories

If it's in the repos it takes one command and a few seconds to install it.

davidtheplatform wrote:

Why would you even need a makefile for a python script? if it just copies the file to /usr/bin or adds a shortcut to the start menu you could just make a normal shell/bash script. You also could bundle it with python using pyinstaller so it works exactly like a normal program and doesn't even need python

MagicCrayon9342 wrote:

davidtheplatform wrote:

Why would you even need a makefile for a python script? if it just copies the file to /usr/bin or adds a shortcut to the start menu you could just make a normal shell/bash script. You also could bundle it with python using pyinstaller so it works exactly like a normal program and doesn't even need python

How is your installer superior to a makefile?

gamer20132020 wrote:

Last login: Sun Oct 15 15:31:01 on console
zain@Kholoods-MacBook-Pro ~ % curl https://raw.githubusercontent.com/GenericProgrammer1234/Noml/main/install.sh -OL && bash install.sh && rm install.sh

% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 1438 100 1438 0 0 3218 0 –:–:– –:–:– –:–:– 3260
Welcome to the Noml installer!
Enter the installation directory for Noml: files
Cloning Noml from GitHub…
Noml installed successfully!
Adding Noml path to PYTHONPATH…
PYTHONPATH updated successfully!
Alias ‘noml’ to the Noml app.py file…
Alias ‘noml’ added successfully!
Installation has finished!
You can now run ‘noml’ to start the text editor.
zain@Kholoods-MacBook-Pro ~ % noml
/Library/Frameworks/Python.framework/Versions/3.11/Resources/Python.app/Contents/MacOS/Python: can't open file ‘/Users/zain/noml/Noml/app.py’: No such file or directory
zain@Kholoods-MacBook-Pro ~ % cd files
zain@Kholoods-MacBook-Pro files % noml
/Library/Frameworks/Python.framework/Versions/3.11/Resources/Python.app/Contents/MacOS/Python: can't open file ‘/Users/zain/Files/noml/Noml/app.py’: No such file or directory
zain@Kholoods-MacBook-Pro files %

__Falcon-Games__ wrote:

curl https://raw.githubusercontent.com/GenericProgrammer1234/Noml/main/install.sh -OL && bash install.sh && rm install.sh

curl https://raw.githubusercontent.com/GenericProgrammer1234/Noml/main/install.sh | bash

ajskateboarder wrote:

__Falcon-Games__ wrote:

curl https://raw.githubusercontent.com/GenericProgrammer1234/Noml/main/install.sh -OL && bash install.sh && rm install.sh

How come nobody here has heard of pipes?

curl https://raw.githubusercontent.com/GenericProgrammer1234/Noml/main/install.sh | bash