Explore >> Select a destination
|
You are here 
|
snapcraft.io | ||
| | | | |
www.deezer.com
|
|
| | | | | Your Weekly Source for Linux GNews from the TuxDigital Network (https://tuxdigital.com/)! | |
| | | | |
popey.com
|
|
| | | | | This is a bit of a dayjob post, but as I maintain a bunch of snaps in my own time, I figured its not out of place here. Typically when I (or indeed any developer) uses snapcraft to build a snap, a snapcraft.yaml drives the process. Ill integrate some kind of CI or build system, and start publishing to the Snap Store. Usually, once created, the yaml doesnt need much in the way of changes. | |
| | | | |
blog.jak-linux.org
|
|
| | | | | Today, I got an email from an user of one of my Python scripts asking why the script t does not work on Arch Linux anymore. As it turns out, the Arch Linux team decided to switch /usr/bin/python to Python 3.0 and use python2 for Python 2.X versions. By doing this, they decided to make their distribution incompatible to almost any Python script in the world. Arch Linux's decision to diverge from the rest of the world that uses python for Python 2.X and python3 for Python 3.X is stupid. And doing this without updating reverse dependencies beforehand and thus breaking packages in their own distribution is insane.In the end this means that if you use Arch Linux, you should consider switching to a distribution that does things the right way: Debian. You can also switch to Ubuntu, that's normally just a bit less right (= faster). But using a distribution that does those crazy things in such an irresponsible way is really insane. | |
| | | | |
enterprisecraftsmanship.com
|
|
| | | My new online training course about Encapsulating EF Core Usagewent live. | ||
