> Well, I think it's either that or use a github-generated source tarball > from the appropriate commit. > > (It's not inherently breaking its own license BTW; the copyright holder > doesn't need a license and can distribute binaries to whoever he likes. > As it stands, it's just impossible for anyone else to legally > redistribute those binaries...)
Well, the github repo doesn't have tags or premade downloads ready: we'd have to pick commit. It looks like he's marking his version-update commits: https://github.com/mikepj/XRG/commit/ca9fe709eae79fab3a4eeffbf67d5c4009013d4c https://github.com/mikepj/XRG/commit/61c485063078d54985c9ae11da7a13d4ba4085f8 I'll switch it back to using source builds, and avoid the binary distfiles. _______________________________________________ macports-dev mailing list [email protected] http://lists.macosforge.org/mailman/listinfo/macports-dev
