Store per-project pycicle settings in the project being tested

[biddisco]

Allow pycicle to take its per project settings from the source project itself.

Each project that uses pycicle for testing can have a pycicle subdir that stores the testing/config settings, the main advantage being

• The settings for the project can be maintained by the project owners without modifiying pycicle
• Different branches could (in principle) have different test settings
• Changes to options can be smoothly updated by the project

and lots more reasons

[PDoakORNL]

Going to start working on this to support other projects. For now I'm considering making a dev branch so as not to disrupt your hpx infrastructure but I am not intending a fork so we should discuss when you have time.

[PDoakORNL]

• Each trunk should not require a project level directory under config

[biddisco]

I'm very happy that you are helping. We have the potential to make a really very useful build tool that handles all our projects' requirements if we add all the features we're considering.

[PDoakORNL]

Yes I think so too. From: John Biddiscombe <notifications@github.com> Reply-To: biddisco/pycicle <reply@reply.github.com> Date: Thursday, May 24, 2018 at 5:20 AM To: biddisco/pycicle <pycicle@noreply.github.com> Cc: "Doak, Peter W." <doakpw@ornl.gov>, Assign <assign@noreply.github.com> Subject: Re: [biddisco/pycicle] Store per-project pycicle settings in the project being tested (#14) I'm very happy that you are helping. We have the potential to make a really very useful build tool that handles all our projects' requirements if we add all the features we're considering. — You are receiving this because you were assigned. Reply to this email directly, view it on GitHub<#14 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/ALTrNFXmPT0-HW_WBRGOQRubhIW1RLuoks5t1ntpgaJpZM4R98mk>.