On Oct 5, 2012, at 11:59 AM, Ryan Schmidt wrote:
> You can remove the "name" line; github.setup sets it for you.
OK.
> You can remove the master_sites line; github.setup sets it for you.
OK.
>> use_bzip2 yes
>
> Most projects on github use gz files not bz2 files. Certainly the automated
> tarballs github can generate for tags or revisions are gz files (or zip
> files). Though for projects that post their own downloads
> ("github.tarball_from downloads") they could be in any format the developer
> wanted to use. csvdb doesn't seem to have posted any downloads however.
OK.
> Yes you're right. It would be best if the developers would create a tag for
> 0.5.1 and any other versions they've released. Sorry; I hadn't realized that
> they hadn't done that already. You should ask them to do this. It's a normal
> part of a software release cycle.
Will check how to contact the author.
> Failing that, yes, you'd need to continue to specify a changeset. I think you
> can do it this way:
>
> github.setup darkrose csvdb afad8eca960af3b61b0a8ee3e1c3e0db4cc5c8f5
> version 0.5.1
Yeah, just a minute ago I figured that.
Thanks Ryan for all your advice. I guess now I should be able to rework the
portfile nicely.
_______________________________________________
macports-dev mailing list
macports-dev@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo/macports-dev
