'importing' thirdparty sources

Giorgos Keramidas keramida at ceid.upatras.gr
Mon Jul 16 10:03:32 CDT 2007


On 2007-07-16 17:49, Giorgos Keramidas <keramida at ceid.upatras.gr> wrote:
> Is there _any_ way to track thirdparty source "in the tree", but avoid
> breaking their original timestamps?  From my reading of the FAQ entry at
> [1] it seems like the answer is "no".
> 
> [1] http://www.selenic.com/mercurial/wiki/index.cgi/FAQ#head-1e601b3d2b1e1c8481ebbe9a47d4acbc4d8c3dd3
> 
> If the answer is indeed "no", what is an alternative of handling
> thirdparty sources with this sort of dependencies to other files in the
> same source tree?

I forgot to mention how this relates to the contrib/ tree of the FreeBSD
source tree.

In the src/ tree of FreeBSD we keep an src/contrib/ subdirectory with
the 'virgin' sources of thirdparty components.  These sources are not
necessarily modified by the FreeBSD team.  In fact, we try to keep our
changes to this part of the tree to the absolutely minimal set of
commits needed, and we even refrain from committing on top of the "CVS
vendor branch" (preferring to pull the fix from the vendor branch when
it is committed upstream).

The import of autoconf-2.61 in a clean Hg workspace which I did earlier
today was an experiment to see how/if Hg can support this sort of
workflow.

Apparently, any thirdparty source which depends on timestamps for the
checked out sources is going to break if we do this.  So this thread is
sort of a question:

``How can we deal with parts of an Hg workspace which are thirdparty
sources (possibly including some local changesets on top of periodic
imports of 'clean' copies)?''

- Giorgos



More information about the Mercurial-devel mailing list