News for hackers. Stuff that matters.

A comment on TUIs. Parent comment

Re:TUIs by lelanthran on Thursday March 17, 2022 @01:09AM (#30707868)
> I'm in the habit of keeping a text file with all software I've installed and updating it immediately. Really helps remember stuff like this.

Coincidental - I just reinstalled my machine and this is the first site I came to. I keep all the applications I installed in a 'packages.new' file, and do

    apt-get install -y `cat packages.new`
when I get a new machine.
[ Parent | on HN ]
Re:TUIs by betwixthewires on Thursday March 17, 2022 @01:12AM (#30707888)
How do you keep track when installing appimages, flatpaks, tarballs, compiling source and things like that?
[ Parent | on HN ]
Re:TUIs by II2II on Thursday March 17, 2022 @07:40AM (#30709982)
It's not quite the same, but I keep a similar file that notes: installed packages from the distribution repository, installed packages from AUR, enabled services, and installed extensions from programs where they can be installed from the command line. (Plus I'll note what has been removed, so I don't forgetfully install things that I've had problems with in the past.) Since everything is one item per line with few extraneous notes, it is easy to pull into Vim and modify into a script.

Properly taken notes are much more than a memory aide.

[ Parent | on HN ]
Re:TUIs by lelanthran on Thursday March 17, 2022 @04:48AM (#30708943)
> How do you keep track when installing appimages, flatpaks, tarballs, compiling source and things like that?

Hey, I didn't claim it was exhaustively complete :-)

I have not used any appimages or flatpaks much. If I am using a program and it is not available on my new install, I'll remember to install it when I look for it.

For source compilation, it's frequently for a once-off use (maybe the repo software is too old, so I compile the latest). Mostly, when I move to a new version I don't need to recompile from source.

[ Parent | on HN ]