Hi, I am currently working on project that I’m calling Installies. It is a tool for Linux that makes it easy to find and use bash scripts to install, remove, update, or compile apps. You can add specific scripts for different distros or architectures.
I have been working on this for the past couple of months, and it is nearly ready to be released. Lately I realized that I haven’t asked any other Linux users if they would find it useful, so if you could tell me if you might find it useful, or any advice/feedback, it would be greatly appreciated. Thanks!
If the project is useful for you and you’re happy with code and documentation: release it.
It would be easier for me to understand if you can explain how this is different from the various other methods of installing software onto a computer.
- How is this different from a package manager, or something like FlatPak or AppImage, where you can find scripts (not necessarily bash scripts) to install whole packages from a binary repository?
- How is this different from Nix or Guix, which provides a method of automatically setting up a shell environment with all dependencies ready for you to build a piece of software from its source code?
- Is there an advantage to your solution over something like OhMyZsh, which provides a repository of Zsh functions you can install to configure the Zsh user interface.
- Is there a reason why, if someone does not want to use a package manager, or Nix/Guix, they would prefer to use your solution rather than just go to the website and find the script there to install the software they need?
- It is different from a package manager because it isn’t platform specific because you can add scripts for any distro or architecture.
- It isn’t really comparable to something like that because it just stores and runs bash scripts to install stuff.
- It can install any app, from anywhere, not just specific to zsh.
- It’s mostly convenience. Also, not all websites have a script to remove once installed, or automated ways to update.
it isn’t platform specific because you can add scripts for any distro or architecture.
…
it just stores and runs bash scripts to install stuff
…
to remove once installed, or automated ways to update.
Well, any Linux distro has a package manager which you can use to install, update, or remove software. So can Nix, Guix, AppImage, and FlatPak. And Nix and Guix allows you to build from source code.
So I guess my question is, if I were thinking about using your app to install software, and update and remove it, how is it more convenient than using my ordinary package manager? If it is more convenient for building software from source, how is it more convenient than Nix or Guix?
Flatpak isn’t distro specific either, is it?
Just drop it! I like the idea. Who cares if it’s going to be used by a lot of people. You enjoyed making it, you make others happy, people might enjoy contributing, and you give inspiration to the community. That’s all that matters.
You rock! Thanks for creating this.
It doesn’t really matter if it’s usefull for others. Write it for yourself and learn from it. I myself wrote copying script for terminal and I am sure no one else going to use it just me and thats fine.
I’m all for building new tools!
You might want to take a hard look at a lot of the ways Homebrew works to find similar problems you’ll need to solve to make this production ready.
if it’s useful to you it might be useful for someone out there, I say go for it
To be honest, there is a class of problems that are extremely common, like maintaining installations, deployment scripts, logging, argument parsing. Apparently you tool belongs to this “really common” problems.
There is also a class of people who tend to solve problems by programming, and prefer doing so before doing some sort of exhaustive research for existing solution. Apparently you belong to this class of people.
I love that this class of people is here (hey, I’m part of it!), having this creative mindset is superb for learning and growing, and for keeping it fun (that’s really important! it’s dangerous to go without fun!).
I say, if you really get joy from solving problems this way then definitely keep this. Perks of being in this “class” is that we often grow attached to our projects and watching it not succeed can be painful.
So just remember to not put all the eggs into one basket: it’s good to realize when you’re in a domain where lots of mature solutions exist so success requires (sans impossible luck) being way much better than the existing ones. Because it can mean that getting people to try out your solution can be disproportionately harder than it “should be” given quality of it. You might need to prepare yourself for a long season of being the only user. On the other hand, looking for beta testers or reviewers, can be a different thing.
Just to make clear, I don’t want this to sound discouraging in any way – it’s just personal experience and failure that might be good for others to not repeat.
I think the fact that, eg. on pypi there are tons of logging and argument parsing libraries shows the overlap between these classes of problems. Another thing is that most of these libraries is going to be abandoned. Again, I think that overall it’s a good way – it means that lots of people love coding and are trying – it’s humanity’s way of getting awesome things.
I want to see it.
I really honestly wish more Linux users would throw open their personal libraries of scripts that made their lives easier. Yes, probably 99% of them are super idiosyncratic to do This One Thing the user needed done or are the same ten or fifteen everyone has discovered for themselves but I bet most of them have a piece of code in them that’s does this thing I didn’t know I could automate or could be a template for this other thing I want to do and didn’t even know where to start or I just want to look at and go ‘wow, you really went all out with that, this is art I want to frame this, holy shit’ even though all it does is like move a file.
No.
