<div dir="ltr"><div>Hello everyone,</div><div><br></div><div>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.</div><div><br></div><div>Thoughts? Opinions? Let's have a discussion in the Trac ticket.</div><br clear="all"><div><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div>-- </div><div>Jason Liu</div></div></div></div><br><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">---------- Forwarded message ---------<br>From: <strong class="gmail_sendername" dir="auto">MacPorts</strong> <span dir="auto"><<a href="mailto:noreply@macports.org">noreply@macports.org</a>></span><br>Date: Sun, Oct 29, 2023 at 9:54 AM<br>Subject: [MacPorts] #68587: pg github: create new 1.1 version<br>To: <br>Cc: <<a href="mailto:jasonliu@umich.edu">jasonliu@umich.edu</a>>, <<a href="mailto:macports-tickets@lists.macports.org">macports-tickets@lists.macports.org</a>><br></div><br><br>#68587: pg github: create new 1.1 version<br>
-------------------------+-----------------------<br>
Reporter: jasonliu-- | Owner: (none)<br>
Type: enhancement | Status: new<br>
Priority: Normal | Milestone:<br>
Component: ports | Version: 2.8.1<br>
Keywords: portgroup | Port: pg-github<br>
-------------------------+-----------------------<br>
I'm proposing that we create a new {{{github 1.1}}} PortGroup that lives<br>
along-side the existing {{{github 1.0}}} PortGroup. The only difference is<br>
to set the default {{{tarball_from}}} to be {{{archive}}}, so that<br>
Portfile writers don't need to add an extra {{{tarball_from archive}}}<br>
line to their portfiles just to achieve what should be the default<br>
behavior. By making it a new 1.1 PortGroup and also keeping the 1.0<br>
PortGroup around, it maintains backwards compatibility, so that we don't<br>
break the checksums for dozens, maybe hundreds of existing ports that are<br>
using the 1.0 PortGroup and may still be fetching from the legacy/dummy<br>
URLs.<br>
<br>
-- <br>
Ticket URL: <<a href="https://trac.macports.org/ticket/68587" rel="noreferrer" target="_blank">https://trac.macports.org/ticket/68587</a>><br>
MacPorts <<a href="https://www.macports.org/" rel="noreferrer" target="_blank">https://www.macports.org/</a>><br>
Ports system for macOS<br>
</div></div>