dot.me VS misc-updater

You can see https://github.com/podiki/dot.me/tree/master/x11 for more, but that is the important part.

In case it helps, you can see my configs for both in my dot files: https://github.com/podiki/dot.me I recently did a lot with my Stump config as I was energized by returning to it, doing things I didn't realize I could do before. It does need cleaning up now.

I have a similar setup to what you are asking about, I think. I haven't migrated everything to org-mode, but many are. You can see my dotfiles here: https://github.com/podiki/dot.me

So you should be able to have just about everything in user profiles/manifests and probably it is a search path here not being exported. If it is helpful, I have my config stuff here https://github.com/podiki/dot.me (see the guix and zsh directories specifically)

I better get right on it! If you are curious, you can see my current Guix config here [0], though not very commented. But those files (combined with the rest of my dot files) would reproduce this system configuration.

[0] https://github.com/podiki/dot.me/tree/master/guix/.config

I use org-mode to generate my file (see https://github.com/podiki/dot.me for all of them), with the main emacs org file weighing in at 72K or 1,865 lines (woah, it got long). While my .emacs file that will load this file is just 5.8K or 106 lines. I've been using, and customizing, emacs for a while...

Personally, I use git [0] along with GNU stow [1], combined with making the files directly from a literate Readme.org (e.g. [2]). I sync this repository between machines to update files, and when I make changes in the org-mode Readme file it automatically generates the new file. There are ways to pull in changes made to that file directly, but haven't needed to do that. My repo doesn't have the full details, but if you want to see it in action along with a few links and pointers, do take a look at [0]. I really like having it all together in one place, and with org-mode everything is very (human) readable.

[0] https://github.com/podiki/dot.me

[1] https://www.gnu.org/software/stow/

[2] https://github.com/podiki/dot.me/blob/master/x11/README.org

I have it running with a very similar setup (same picom fork, XMonad, nvidia, xinitrc), which you can see here, in case it helps: https://github.com/podiki/dot.me

STOW is great, it is simple and works well especially combined with git. That's what I do [0], and recently combined it with org-mode for literate programming, so each program has just a README.org that then generates all the files via org tangle [1] [2]. For example, here is my file that generates my Xorg configuration [3] over several files, nicely readable on GitHub, in Emacs, or just as plain text.

[0] https://github.com/podiki/dot.me/

[1] https://web.archive.org/web/20190924102437/https://expoundit...

[2] https://orgmode.org/manual/Working-with-Source-Code.html

[3] https://github.com/podiki/dot.me/tree/master/x11

> Ubuntu Flavors Agree to Stop Using Flatpak

Yayy!!!

> And to focus their efforts exclusively on deb,

Yayyy!!!

> and snap.

... oh.

Honestly I avoid flatpak/snap/etc like the plague. Every time I've used them, some sort of device or file can't be accessed, or something isn't working. If I need anything that isn't covered by apt repositories, I just compile from source now, and have my own system for detecting updates which works pretty well. (https://github.com/tpapastylianou/misc-updater if anyone's interested).

I have a nice little script for managing "MISC" packages: Manually Installed or Source Compiled.

https://github.com/tpapastylianou/misc-updater

In full honesty, I'm as proud of the "MISC" acronym as of the script itself. I'm secretly hoping the acronym catches on for referring to any stuff outside the control of a system's standard package management.

What do people use to check for updates when it comes to programs they installed manually / compiled from source instead of relying on their distro's repositories?

I made this for myself for this purpose: https://github.com/tpapastylianou/misc-updater

(pretty chuffed about the MISC acronym btw :p )

Often enough, when I see something like this, the real value isn't the software itself, but the idea that perhaps the issue it addresses is be worth thinking about a bit more. The solution itself may be trivial, but have a large impact.

E.g. I have created [0] the simplest of scripts for managing updates for manually-installed / source-compiled applications (something I've dubbed "misc", very proud of this backronym :p).

The script itself is extremely simple (just a list of greps over latest release announcement urls), but it has solved a big problem for me, of helping me keep such "misc" items seamlessly up-to-date.

[0]: https://github.com/tpapastylianou/misc-updater