• 0 Posts
  • 83 Comments
Joined 11 months ago
cake
Cake day: December 5th, 2023

help-circle
  • Well personally if a package is not on aur I first check if there’s an appimage available, or if there’s a flatpak. If neither exist, I generally make a package for myself.

    It sounds intimidating, but for most software the package description is just gonna be a single file of maybe 10-15 lines. It’s a useful skill to learn and there’s lots of tutorials explaining how to get into it, as well as the arch wiki serving as documentation. Not to mention, every aur or arch package can be looked at as an example, just click the “view PKGBUILD” link on the side on the package view. You can even simply download an existing package with git clone and just change some bits.

    Alternatively you can just make it locally and use it like that, i.e. just run make without install.


  • Aur and pacman are 90% of why I use arch.

    Also fyi to OP: never install software system-wide without your package manager. No sudo make install, no curl .. | sudo bash or whatever the readme calls for. Not because it’s unsafe, but because eventually you’re likely to end up with a broken system, and then you’ll blame your distro for it, or just Linux in general.

    My desktop install is about a decade old now, and never broke because I only ever use the package manager.

    Of course in your home folder anything goes.



  • What’s up with the abuse of the word open lately. I had a look at that project to see how they were doing the conversion, but I couldn’t find it. But I found this:

    Short answer, yes! OpenScanCloud (OSC) is and will stay closed source…

    Your data will be transferred through Dropbox and stored/processed on my local servers. I will use those image sets and resulting 3d models for further research, but none of your data will be published without your explicit consent!

    I feel like I’d rather use Autodesk at that point. At least I know what I’m dealing with right out of the gate.





  • Well I’m not sure it takes an expert to master a plug.

    But I’d understand the hate if it was universal (pun maybe intended), but everyone that hates micro-usb seems to adore usb-c, while I feel like it’s potentially much more fragile. When handling usb-c I always use a lot more delicate care than I ever did with micro-usb. Mostly because even though I’m pretty good at soldering very tiny things, I’m not confident I could replace most usb-c receptacles without messing it up.










  • It’s easy to understand them when you realise that their entire ideology starts at “anything the US does or says is bad” and continues from there.

    • The US supports Taiwan and is against China? China good, Taiwan bad.
    • The US supports Ukraine and is against Russia? Russia good, Ukraine bad.
    • Israel, Palestine, same thing
    • Bosnian and Rwandan genocide happened? Well the US says so, therefore they didn’t.
    • NATO bombed Serbia over their attempted genocide in Kosovo. NATO is the US, so Serbia didn’t do anything wrong, but Kosovo is bad.
    • And so on, and so on…

    Once you look at it through that lens, even their most wild takes suddenly become very consistent.



  • I’ve been in love with the concept of ansible since I discovered it almost a decade ago, but I still hate how verbose it is, and how cumbersome the yaml based DSL is. You can have a role that basically does the job of 3 lines of bash and it’ll need 3 yaml files in 4 directories.

    About 3 years ago I wrote a big ansible playbook that would fully configure my home server, desktop and laptop from a minimal arch install. Then I used said playbook for my laptop and server.

    I just got a new laptop and went to look at the playbook but realised it probably needs to be updated in a few places. I got feelings of dread thinking about reading all that yaml and updating it.

    So instead I’m just gonna rewrite everything in simple python with a few helper functions. The few roles I rewrote are already so much cleaner and shorter. Should be way faster and more user friendly and maintainable.

    I’ll keep ansible for actual deployments.


  • Not sure what you’re on about, most package managers have a literal database of most package manager installed files. Debian and derivatives have dpkg --verify or debsums to verify the files, arch has paccheck, I’m sure other distros have something similar. And fixing them is just a matter of reinstalling the package, which you can do from a chroot if the system won’t boot.

    Or you can just run your system on a checksumming FS like btrfs which will instantly tell you when a file goes bad.