From 0dfdf613188ea5fba980055965ee38c9fc519663 Mon Sep 17 00:00:00 2001 From: Vito Caputo Date: Sun, 27 Aug 2023 13:16:36 -0700 Subject: *: switch to https URLs throughout The git:// URLs work fine but they're both easier to MITM (however unlikely) and more likely to be blocked if you're on something like a public library or corporate WiFi blocking everything but 80/443 traffic. Also while updating the README URL I made `git clone --recursive` the assumed supported method, anyone using such an old git can deal. --- .gitmodules | 8 ++++---- README | 10 +--------- 2 files changed, 5 insertions(+), 13 deletions(-) diff --git a/.gitmodules b/.gitmodules index 6d3f95f..e721f5a 100644 --- a/.gitmodules +++ b/.gitmodules @@ -1,12 +1,12 @@ [submodule "libstage"] path = libstage - url = git://git.pengaru.com/libstage + url = https://git.pengaru.com/git/libstage [submodule "libplay"] path = libplay - url = git://git.pengaru.com/libplay + url = https://git.pengaru.com/git/libplay [submodule "libix2"] path = libix2 - url = git://git.pengaru.com/libix2 + url = https://git.pengaru.com/git/libix2 [submodule "libansr"] path = libansr - url = git://git.pengaru.com/libansr + url = https://git.pengaru.com/git/libansr diff --git a/README b/README index 4f1dc31..5d8971f 100644 --- a/README +++ b/README @@ -1,15 +1,7 @@ Building from source: You've probably already done this, but first clone the repo: -`git clone git://git.pengaru.com/sars` - -There are a few submodules which must be initialized recursively -before sars will be able to compile, this does the trick: - -`git submodule update --init --recursive --remote` - -*** New enough git versions support recursive clone too: -` git clone --recursive git://git.pengaru.com/sars` +`git clone --recursive https://git.pengaru.com/git/sars` Now it's fairly run of the mill autotools: -- cgit v1.2.3