![]() We can either choose a branch like stable, or we can choose a release name like Jessie. This can be done in either /etc/apt/apt.conf (which probably does not already exist) or by creating a file in /etc/apt/. We’re about to add Stretch to sources.list, so if we don’t specifically set the default release, our system will start to prefer newer Stretch packages all over. This is important as right now the release we are using (Jessie) is governed by the sources.list file. Configuring Stretch Sourcesįirst off, we need to set our default release. Once again, this method is arguably better than the previous, removing any usage of the lower-level dpkg tool. ![]() Now it’s March, and the lightbulb finally went off in my head that I should use APT’s techniques for mixing packages from different releases for dnscrypt. This is arguably better as the Debian team will have tailored the package to Debian, even if it’s from Stretch rather than Jessie. deb from Debian Stretch (testing) and installing it with dpkg. In February I found out about and wrote about another method – obtaining the. removed) with dpkg, but it’s still not a package tailored for Debian. It’s better than make install in that the package can be managed (e.g. As dnscrypt is not in the Debian Jessie repositories, I installed it using checkinstall which is the same as make install except it creates a. In January I wrote about installing dnscrypt on Debian Jessie (stable). Rather than continue this in a patchwork fashion, I’ve decided to do everything from scratch. Now that I know modern Debian in much more detail, I’m realising many improvements that can be made to the setup. It was pretty much a set-and-forget setup, so my January 2017 posts on this topic were mostly based on my original installation in 2015. I had originally set up dnscrypt-proxy back in late 2015 when I was still learning lots about modern Debian.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |