kangie posted on Sat, 28 Jun 2025 20:49:29 +1000 as excerpted: > 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. > # 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" So I suppose I'm as portage-positive as the next guy, but... Maybe take the opportunity to s/Portage/package manager/ (mangler?) or some such while you're at it? (Or maybe "EAPI compliant package manager" if just PM's too generic, or just PM if it's not considered to ambiguous...) Just seems a bit like tunnel vision to specifically name portage in something like skel.ebuild these days, even if portage /is/ the vast majority, user-side. (Of course doesn't /have/ to be /this/ commit if someone thinks that needs more discussion than the simple s/ftp/https/ stuff or maybe council needs to vote on a change like that... but the discussion would need to start somewhere even if it won't go in this commit, so...) -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman
