On May 22, 2022, at 5:32 AM, Ryan Schmidt wrote:
> It is possible but not permitted to specify "the latest code" (such as a
> Subversion repository trunk or a git repository main or master branch or the
> head of any branch in any revision control system in fact) because if you did
> that, what
You can (for yourself) just change the github commit to HEAD and you’ll get the
latest commit. Disable the checksum phase if you do that.
I often do that in some of my local portfile overlay repos for my own uses, but
you can’t do that for macports in general as Ryan points out as the builds are
On May 21, 2022, at 10:22, Bill Cole wrote:
> I'm currently working on a OSS project (SpamAssassin) which is in a
> pre-release rush and which I ultimately test & deploy via MacPorts.
>
> I'd *like* to be able to switch from the current supported release in
> MacPorts to a fresh build from a Su
On 2022-05-21 at 20:23:49 UTC-0400 (Sat, 21 May 2022 20:23:49 -0400)
Andrew Udvare
is rumored to have said:
If it's off GitHub or GitLab you don't have to create the tarball
unless it
has submodules (you can also fetch multiple tarballs but this is
complex).
In this case (and for many ASF pr
If it's off GitHub or GitLab you don't have to create the tarball unless it
has submodules (you can also fetch multiple tarballs but this is complex).
I actually have a script to update my ports that are of 'latest version'
tarballs.
https://github.com/Tatsh/ports/blob/master/_resources/bin/liveup
On 2022-05-21 at 15:24:23 UTC-0400 (Sat, 21 May 2022 15:24:23 -0400)
Andrew Udvare
is rumored to have said:
> Rather than pull via version control,
Which is MY GOAL, not an incidental mechanical issue.
> grab a tarball with the SHA you want.
Which would mean creating an ad hoc tarball before e
Rather than pull via version control, grab a tarball with the SHA you want.
That's how I do 'latest' version ports.
On Sat, May 21, 2022, 11:23 Bill Cole <
macportsusers-20171...@billmail.scconsult.com> wrote:
> I'm currently working on a OSS project (SpamAssassin) which is in a
> pre-release rus
I'm currently working on a OSS project (SpamAssassin) which is in a pre-release
rush and which I ultimately test & deploy via MacPorts.
I'd *like* to be able to switch from the current supported release in MacPorts
to a fresh build from a Subversion checkout without manually mimicking what MP
d
