Hi Volker, We have implemented mirror support that does what you want: https://github.com/hashdist/hashdist/blob/master/hashdist/core/source_cache.py#L740
Mirrors are specified in the hashdist config file, not profiles, but I don't think it would be hard to add support for mirrors at the profile-level. I don't see a reason to specify mirrors at the package level, which is where we tend to put the canonical source. We don't support sub-commit level Git objects, currently. At this point, you'd need to depend on a commit that contained your git tree. The full commit would be unpacked in the build, and you could do a sub-install from there. I (and the rest of the developers) would probably need to think a bit about the advantages/risks of allowing sub-commit objects to be referenced in package installs. On my first impression, it seems a little low-level for HashDist's layer of responsibility. Creating such a subtree commit object is not hard for an advanced Git developer, however... A -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
