Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
mercurial
Home
+ new post
About this group
Join this group
Message from discussion hg subrepositories always on tip?
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
paul_nat...@selinc.com  
View profile  
 More options Mar 2 2012, 3:49 pm
From: paul_nat...@selinc.com
Date: Fri, 2 Mar 2012 12:49:00 -0800
Subject: Re: hg subrepositories always on tip?
Print | View thread | Show original | Report this message | Find messages by this author

This concept is used by IBM ClearCase, and is called a Config
Specification aka config spec. I highly encourage anyone interested in
enterprise-class subrepo implementation to go study config specs. While
ClearCase has some special problems, config specs solve source control
configuration pretty nicely (and confuse the uninitiated badly... ).

The need to point components onto branches/versions/tags/tip/etc, and then
to maintain hg in a state where those pointers are 'valid' of that is very
evident when dealing with large-scale codebases (multiple components,
multiple projects, multiple products).

We've had to implement a hacky version of it ourselves; we use a top level
repo and have a script move every subrepo to the head of the current named
branch that the top-level repo points to.

I anticipate that eventually subrepos will have this functionality (either
native or scripted by most largescale implementors of hg).

- - -
Regards,
Paul Nathan

mercurial-boun...@selenic.com wrote on 03/02/2012 10:23:43 AM:

> From: Scott Palmer <swpal...@gmail.com>
> To: Todd Greer <TGr...@affinegy.com>
> Cc: "mercur...@selenic.com" <mercur...@selenic.com>
> Date: 03/02/2012 10:24 AM
> Subject: Re: hg subrepositories always on tip?
> Sent by: mercurial-boun...@selenic.com

> On 2012-03-02, at 11:58 AM, Todd Greer wrote:

> > Tobias Werth said:

> >> Is there a more convenient way for Bob to tell HG that he always
> wants to use the the tip of the sub repository as state?

> > I'm in the middle of setting up our continuous integration
> systems, and I'm taking the approach of having the build scripts
> pull and update select subrepos, and then committing and pushing the
> superrepo. I'm not done, so I can't say whether there are any major
> issues yet. Alternatively, you might install an update hook on the
> super-repo that pulls and updates select subrepos.

> > It would be convenient for there to be a built-in way to do this;
> something like "hg sync subrepo1 subrepo2 subrepo3", which would
> pull and update listed subrepos, then commit and push the superrepo.

> > --
> > Todd

> I was thinking there should be a way to force subrepos to the tip
> revision in some cases as well.  Particularly when you are working
> on the tip of your main development branch and you want to make sure
> you are compiling against the latest version of some shared code.
> (I.e. you are using an API that is also currently in development by
> a colleague.)

> For example if the parent repo is at the tip, then perhaps something
> like "hg update -S" in the parent could have an option to bring the
> subrepos to their respective tip revisions.  Perhaps an extra option
> would be needed.  Maybe even an extra section in the .hgsub file
> could be used to indicate which subrepos you would like that rule to
> apply to, since there could be some subrepos that you do wan tho
> keep pinned unless they were explicitly updated from within the subrepo.
> E.g in .hgsub:

> subrepo= <url_to_repo>
> othersubrepo = <url_to_other_subrepo>

> [subPath]
> http://(.*)/ParentProject/subrepo = http://\1/SharedLibraries/subrepo

> [subTip]
> subrepo = pinned
> othersubrepo = latest

> Where the [subTip] section tells Mercurial which subrepos should be
> updated to their latest revision when the parent is updated to "tip"

> Scott

> _______________________________________________
> Mercurial mailing list
> Mercur...@selenic.com
> http://selenic.com/mailman/listinfo/mercurial

_______________________________________________
Mercurial mailing list
Mercur...@selenic.com
http://selenic.com/mailman/listinfo/mercurial


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2013 Google