Subject: Re: [boost] Request for a new submodule, tools/depinst
From: Daniel James (dnljms_at_[hidden])
Date: 2016-11-11 15:15:39
On 11 November 2016 at 20:07, Rene Rivera <grafikrobot_at_[hidden]> wrote:
> On Fri, Nov 11, 2016 at 3:02 PM, Daniel James <dnljms_at_[hidden]> wrote:
>> On 11 November 2016 at 19:42, Peter Dimov <lists_at_[hidden]> wrote:
>> > It does work for pull requests. See for instance
>> > https://github.com/boostorg/serialization/pull/48
>> Oh okay, sorry, I didn't realise $TRAVIS_BRANCH was the target branch
>> for pull requests. It still doesn't work for other branches though,
>> which would be an issue for me as that's where I rely on travis.
> You mean for other clones? If you have your own Travis account you can add
> the clone to your account and get the same testing run there.
I was referring to Peter's script which uses $TRAVIS_BRANCH for the
super project. In my modules, I just use a stable release, but if I
wanted a new version of a dependency, I'd do what Andrey suggested,
and use a specific version of the super project (i.e. a tag or a
commit's hash) rather than a branch.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk