I didn’t like the capitalised names so configured xdg to use all lowercase letters. That’s why ~/opt fits in pretty nicely.

You’ve got a point re ~/.local/opt but I personally like the idea of having the important bits right in my home dir. Here’s my layout (which I’m quite used to now after all these years):

$ ls ~
bin  
desktop  
doc  
downloads  
mnt  
music  
opt 
pictures  
public  
src  
templates  
tmp  
videos  
workspace

where

• bin is just a bunch of symlinks to frequently used apps from opt
• src is where i keep clones of repos (but I don’t do work in src)
• workspace is a where I do my work on git worktrees (based off src)

Thanks! So much for my reading skills/attention span 😂

Which Debian version is it based on?

RE Go: Others have already mentioned the right way, thought I’d personally prefer ~/opt/go over what was suggested.

RE Perl: To instruct Perl to install to another directory, for example to ~/opt/perl5, put the following lines somewhere in your bash init files.

export PERL5LIB="$HOME/opt/perl5/lib/perl5${PERL5LIB:+:${PERL5LIB}}"
export PERL_LOCAL_LIB_ROOT="$HOME/opt/perl5${PERL_LOCAL_LIB_ROOT:+:${PERL_LOCAL_LIB_ROOT}}"
export PERL_MB_OPT="--install_base \"$HOME/opt/perl5\""
export PERL_MM_OPT="INSTALL_BASE=$HOME/opt/perl5"
export PATH="$HOME/opt/perl5/bin${PATH:+:${PATH}}"

Though you need to re-install the Perl packages you had previously installed.

This is fantastic! 👏

I use Perl one-liners for record and text processing a lot and this will be definitely something I will keep coming back to - I’ve already learned a trick from “Context Matching” (9) 🙂

That was my case until I discovered that GNU tar has got a pretty decent online manual - it’s way better written than the manpage. I rarely forget the options nowadays even though I dont’ use tar that frequently.

TBH I use whatever build tool is the better fit for the job, be it Gradle, SBT or Rebar.

But for some (presumably subjective) reason, I like GNU Make quite a lot. And whenever I get the chance I use it - esp since it’s somehow ubiquitous nowadays w/ all the Linux containers/VMs everywhere and Homebrew on Mac machines.

I’m nitpicking but can you properly quote your code?

That single line of Lisp is probably (defmacro generate-compiler (...) ...) which GCC folks call every time they decide to implement a new compiler 😆

That’s a fair point 👍 I just wanted to point out that I’m not the author.

As I said, I very much like the idea. It helps raise awareness around the current trend of switching licenses to curb competition/make $$$.

a list or database of projects that were open but then closed down

That’s a great idea! Esp if the list is actively maintained & updated.

Since I am NOT the author of this extension, do you think you could write down your thoughts on the project’s issue tracker?

Created an issue on the repo: https://github.com/galdor/github-license-observer/issues/5

It is: https://opensource.org/license/mit/

It’s most probably a bug in the addon. Best to report it on the repo’s issue tracker: https://github.com/galdor/github-license-observer/issues

Oops! My mistake 🤦 Updated the post.

I agree w/ you RE posts looking horrible 👍

Though I’d say for one-liners like this, it’s mostly OK. It gets really messy when folks post more complex posts and mention and tag a bunch of times.

I’m afraid I can’t be of any help 😕

Any error logs? Try launching things from the terminal and note down any messages that are printed there.

That’s a good question 💯 In my case too, it took me some time (read years 😂) to figure out what I’m comfortable w/.

I can think of 3 major ways that you can navigate the filesystem while being able to drop to a shell when you need it:

• If you’re familiar w/ Emacs, you can either:
  • Use dired and tramp on your machine to access/navigate the target machine.
  • Install Emacs (emacs-nox) on the target machine, SSH and then run emacs-nox and voila! No need for tramp in this scenario.
• Use Midnight Commander (mc) which offers a TUI pretty much like Norton Commander (nc) from the days of yore.
• Get used to the semi-standard structure of the file system and just use plain Bash (cd, pushd & popd) to move around. That is
  • Understand what usually goes into common directories (like /usr/share or /opt) and try to follow the same pattern when rolling your own software installations.
  • Learn how to use your distro’s package manager to query packages and find out where things, like configurations and docs, are stored. Something as simple as rpm -q --list is what you usually need.

HTH

messing with the partition any more than I already have

Running fsck is a harmless and actually pretty useful operation, esp if you boot using a USB stick.

But yes, never hurts to have backups - easier said than done 😂