Hello everyone,
After yet one more reminder from one of the committers to add
"github.tarball_from archive" to my Portfile, it was the straw that broke
this camel's back, and I have decided to do something about it. So I've
created a Trac ticket to make a new github 1.1 PortGroup, that sets the
default "tarball_from" to be "archive", so that we don't need to add an
extra line just to achieve what should be the default behavior.
Thoughts? Opinions? Let's have a discussion in the Trac ticket.
--
Jason Liu
---------- Forwarded message ---------
From: MacPorts <nore...@macports.org>
Date: Sun, Oct 29, 2023 at 9:54 AM
Subject: [MacPorts] #68587: pg github: create new 1.1 version
To:
Cc: <jason...@umich.edu>, <macports-tick...@lists.macports.org>
#68587: pg github: create new 1.1 version
-------------------------+-----------------------
Reporter: jasonliu-- | Owner: (none)
Type: enhancement | Status: new
Priority: Normal | Milestone:
Component: ports | Version: 2.8.1
Keywords: portgroup | Port: pg-github
-------------------------+-----------------------
I'm proposing that we create a new {{{github 1.1}}} PortGroup that lives
along-side the existing {{{github 1.0}}} PortGroup. The only difference is
to set the default {{{tarball_from}}} to be {{{archive}}}, so that
Portfile writers don't need to add an extra {{{tarball_from archive}}}
line to their portfiles just to achieve what should be the default
behavior. By making it a new 1.1 PortGroup and also keeping the 1.0
PortGroup around, it maintains backwards compatibility, so that we don't
break the checksums for dozens, maybe hundreds of existing ports that are
using the 1.0 PortGroup and may still be fetching from the legacy/dummy
URLs.
--
Ticket URL: <https://trac.macports.org/ticket/68587>
MacPorts <https://www.macports.org/>
Ports system for macOS
