From: Matt Jolly <[email protected]> In 2025 FTP is increasingly uncommon. The world we live in is (mostly) HTTPS, and SRC_URI should reflect that.
Add additional commentry about (and use SRC_URI to show an example of) renaming the distfile with `->` when required. Signed-off-by: Matt Jolly <[email protected]> --- skel.ebuild | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/skel.ebuild b/skel.ebuild index 437e0d5c569d..29e679528778 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/v${PV}.tar.xz -> ${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
