I use ~/local for compiling packages without root. It emulates
/usr/local, basically. So sometimes it might have .pc files etc in
corresponding pkgconfig/ in there or .so files in corresponding lib/.
I do this because I almost always don't have root, because I work on
tildes primarily (tilde.cafe to be specific) so yeah. If a package is
written in go or similar where building would be easy, the basic
workflow is this:
cd ~/local/src
git clone git@example.com:user/repo
cd repo
make PREFIX="$HOME/local" install
If all goes well the binary would be available at ~/local/bin.
For apt packages there is a higher chance of build failing and most of
them need other dependencies (plus some other historical reasons idk) so
I don't use ~/local/src[1], here's the general workflow:
cd ~/Downloads
apt source pkgname
cd pkgname
ls -A
less INSTALL
./configure --prefix=~/local
make PREFIX=~/local
make install PREFIX=~/local
And most likely it would complain about some package not found in the
configure step, in which case I woukd repeat the steps for that package.
Eventually (if I hadn't given up yet), the binary would be sitting in
~/local/bin nicely.
Sometimes the package needs a lot of dependencies, in that case it may
take up a shit ton of disk space, so I would pack it in a .tar.gz so it
can be saved for future use.
For meson projects:
cd ~/local/src
git clone git@example.com:user/repo
ls -A
meson setup build
meson compile -C build
meson install -C build --destdir ~/local
rsync ~/local/usr/local/ ~/local/ -avr
rsync ~/local/usr/ ~/local/ -avr && rm -rf ~/local/usr
I don't use meson often so I'm unaware of a way to easily specify
PREFIX, if any.
So that's my life of getting stuff installed without root. Thanks for
coming to my ted talk. One day I'll probably copy this entire commit msg
and make it into a blog post.
Same as pushall alias but omits the --all so only the current branch is
pushed. I sometimes find this useful when I have a development branch
that isn't ready yet and only want to push the primary branch to all
remotes.
nvim: Setup script install plug only if isn't installed
Part of my effort to make the scripts able to be run >once
--
README: Installation stuff and modify ToC
--
nvim: Add markdown ToC plugin
--
git: Config file tabs to spaces
--
aerc: Use ~/local/share/aerc and add setup script
many many people do this. I didn't do it before because I haven't
bothered to, and I didn't think 3-chara git is THAT much... But today I
was working with yadm (aliased to y) and then immediately switched to
git and undoubtedly 3-chars and 1-char is a huge difference
In any case, I don't think there are much (if not, any at all) cli
scripts with 1 letter names. I can't remember but I'm pretty sure that's
against the 'poetry of cli naming' article :P
wakatime made my nvim startup *extremely* slow, I used vim-profiler and
wakatime takes few thousand times slower than my other plugins, damn
planning to look from or make my own lightweight coding metrics
solution.
* expand tab by default
* add a lot of comments for future me
* improve autocomplete experience a bit
* revamp and fix some mappings
* better plugins and remove unused ones
* ftdetect scd
* Add diagnostics count of lightline
That's it I guess?
Hedy Li
