public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: kangie@gentoo.org
To: gentoo-dev@lists.gentoo.org
Cc: Matt Jolly <kangie@gentoo.org>
Subject: [gentoo-dev] [PATCH v2] skel.ebuild: update SRC_URI
Date: Sat,  5 Jul 2025 17:04:27 +1000	[thread overview]
Message-ID: <20250705070541.399600-1-kangie@gentoo.org> (raw)
In-Reply-To: <20250628105918.341941-1-kangie@gentoo.org>

From: Matt Jolly <kangie@gentoo.org>

In 2025 FTP is increasingly uncommon. The world we live in is (mostly)
HTTPS, and SRC_URI should reflect that.

Add commentry about renaming distfiles with `->` when required.

Signed-off-by: Matt Jolly <kangie@gentoo.org>
---
 skel.ebuild | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/skel.ebuild b/skel.ebuild
index 437e0d5c569d..213761669a41 100644
--- a/skel.ebuild
+++ b/skel.ebuild
@@ -29,8 +29,8 @@ DESCRIPTION="This is a sample skeleton ebuild file"
 HOMEPAGE="https://foo.example.org/"
 
 # Point to any required sources; these will be automatically downloaded by
-# Portage.
-SRC_URI="ftp://foo.example.org/${P}.tar.gz"
+# Portage. If a file needs to be renamed use the "->" syntax.
+SRC_URI="https://files.example.org/foo/${P}.tar.xz"
 
 # Source directory; the dir where the sources can be found (automatically
 # unpacked) inside ${WORKDIR}.  The default value for S is ${WORKDIR}/${P}
-- 
2.49.0



      parent reply	other threads:[~2025-07-05  7:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-28 10:49 [gentoo-dev] [PATCH] skel.ebuild: update SRC_URI kangie
2025-06-28 14:16 ` Ulrich Müller
2025-06-29  1:43   ` Ionen Wolkens
2025-06-29 12:34 ` [gentoo-dev] " Duncan
2025-07-05  7:04 ` kangie [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20250705070541.399600-1-kangie@gentoo.org \
    --to=kangie@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox