WARNING: This server is unstable and will be retired in the next days.
If you want to keep this forum available, please request immediately a migration
on the Nabble Support forum.
Forums that don't receive any migration request will be deleted forever.
> If github has automated downloads available for any tag/branch as well, then we would need to verify that they always have the same checksums, and are not generated on the fly. I'm pretty sure that bitbucket, for example, generates them on the fly, meaning different users requesting them at different times will get different checksums, which means they're not suitable for use as master_sites in MacPorts.
You can see that they both generate the same checksums. For the above
link, the sha1sum reports:
> As I explained in the ticket already, the decision of whether to use the rss feed for livecheck should be based on whether git.branch has been set, not on the length of the version. It does not make sense to set the version to the git hash for the reasons I explained in the ticket.
Ah, ok, I see what you mean about git.branch now. Thanks for
explaining some more.
> I didn't know that we had, or that anyone was working on, a bitbucket portgroup. Is there a ticket already?
No, it's still a patch in my local repo. Since I didn't know how to
proceed with the github group, I was waiting for this to be settled
then I'd submit the bitbucket one.
> What do you mean, "if version exists"? The third parameter of github.setup, which is currently not optional, is the version number you want to assign to this port.
Using the repo above as an example, what version would it get? Now
that I understand what you meant by git.branch, my guess is that it'd
be the following: