<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Package Management on The Lone C++ Coder's Blog</title><link>https://www.lonecpluspluscoder.com/tags/package-management/</link><description>Recent content in Package Management on The Lone C++ Coder's Blog</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Sat, 18 Feb 2017 09:14:25 +0000</lastBuildDate><atom:link href="https://www.lonecpluspluscoder.com/tags/package-management/index.xml" rel="self" type="application/rss+xml"/><item><title>Fixing package download performance problems in Manjaro Linux</title><link>https://www.lonecpluspluscoder.com/2017/02/18/fixing-package-download-performance-problems-manjaro-linux/</link><pubDate>Sat, 18 Feb 2017 09:14:25 +0000</pubDate><author>Timo Geusch</author><guid>https://www.lonecpluspluscoder.com/2017/02/18/fixing-package-download-performance-problems-manjaro-linux/</guid><description>&lt;p>My adventures with Manjaro Linux continue and I&amp;rsquo;ve even moved my &amp;ldquo;craptop&amp;rdquo; - a somewhat ancient Lenovo X240 that I use as a semi-disposable travel laptop - from XUbuntu to Manjaro Linux. But that&amp;rsquo;s a subject for another blog post. Today, I wanted to write about package download performance issues I started encountering on my desktop recently and how I managed to fix them.&lt;/p>
&lt;p>I was trying to install &lt;a href="https://gnometerminator.blogspot.com/">terminator&lt;/a> this morning and kept getting errors from Pamac that the downloads timed out. Looking at the detailed output, I noticed it was trying to download the packages from a server in South Africa, which isn&amp;rsquo;t exactly in my neighbourhood. Pamac doesn&amp;rsquo;t appear to have an obvious way to update the mirror list like the Ubuntu flavours do, but a quick dive into the command line helped me fix the issue.&lt;/p></description></item><item><title>MELPA has a new URL</title><link>https://www.lonecpluspluscoder.com/2014/10/28/melpa-changed-urls/</link><pubDate>Tue, 28 Oct 2014 07:22:42 +0000</pubDate><author>Timo Geusch</author><guid>https://www.lonecpluspluscoder.com/2014/10/28/melpa-changed-urls/</guid><description>&lt;p>&lt;a href="http://melpa.org/">MELPA&lt;/a> has recently got its own domain (&lt;a href="http://melpa.org/">melpa.org&lt;/a>) so it&amp;rsquo;s time to update your list of package repositories with the new URL.&lt;/p>
&lt;p>Speaking of MELPA, I recently switched to their &lt;a href="http://stable.melpa.org/">stable repository&lt;/a> instead of their &amp;ldquo;regular&amp;rdquo; nightly build/snapshot repository after I accidentally ended up with a &lt;a href="https://github.com/clojure-emacs/cider">cider&lt;/a> build that didn&amp;rsquo;t want to playing ball. This is not a complaint - if you use nightly builds etc you know what you&amp;rsquo;re getting yourself into - but it prompted me to switch over to using the stable package repository instead on those machines that I consider production machines. This of course require me to uninstall and reinstall a bunch of packages but that only took a few minutes.&lt;/p></description></item><item><title>I finally started using ELPA</title><link>https://www.lonecpluspluscoder.com/2013/12/14/i-finally-started-using-elpa/</link><pubDate>Sat, 14 Dec 2013 08:00:32 +0000</pubDate><author>Timo Geusch</author><guid>https://www.lonecpluspluscoder.com/2013/12/14/i-finally-started-using-elpa/</guid><description>&lt;p>My normal development workflow doesn&amp;rsquo;t use that many different Emacs packages. With a few exceptions I&amp;rsquo;ve mainly worked with a &amp;ldquo;stock&amp;rdquo; Emacs distribution and augmented that with a few select Emacs packages that I downloaded manually. It worked for me for a decade or so, and it made it reasonable easy to move configurations between machines - zip &amp;amp; copy was my friend for that, although I&amp;rsquo;ve since changed that to using dropbox.&lt;/p></description></item></channel></rss>