Summary: | mercurial.eclass: please add --force to EHG_PULL_CMD | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Chí-Thanh Christopher Nguyễn <chithanh> |
Component: | Eclasses | Assignee: | Krzysztof Pawlik (RETIRED) <nelchael> |
Status: | RESOLVED WONTFIX | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Chí-Thanh Christopher Nguyễn
2009-04-04 23:11:51 UTC
correction to comment 0: that should read EHG_REPO_URI in Step 2 As upstream messing in such way with its repository isn't a common thing I'm quite reluctant to do so. In my opinion defaults in eclass should work for most cases, and are ... defaults - to be overridden by ebuilds. If upstream does not mess with its repository, --force will not make any difference. Do you think there are any cases where this option can break things? The only issue I can think of is two mercurial packages with the same name and in different categories will replace each other's repository on merge (instead of failing), resulting in unnecessary traffic. I think that upstream messing with their repository is happening seldom enough that --force is not needed - in such cases just remove the current working copy and repository. |