FileInPath must handle symbolic links properly

[wmtan]

This PR fixes FileInPath to work properly in the presence of symbolic links in any relevant paths.
Currently, FileInPath does not resolve symbolic links before checking if paths match. This can cause matches to be missed. Since the IB unit tests are now run with a symbolic link to the src directory,
the FWCore/PythonParameterSet unit test was failing due to this issue. This PR should fix the test.

[wmtan]

@cmsbuild please test

[cmsbuild]

The tests are being triggered in jenkins.
https://cmssdt.cern.ch/jenkins/job/ib-any-integration/9872/console

[cmsbuild]

A new Pull Request was created by @wmtan for CMSSW_8_0_X.

It involves the following packages:

FWCore/ParameterSet
FWCore/PythonParameterSet
FWCore/Utilities

@cmsbuild, @smuzaffar, @Dr15Jones, @davidlange6 can you please review it and eventually sign? Thanks.
@Martin-Grunewald, @makortel, @wddgit this is something you requested to watch as well.
@slava77, @Degano, @smuzaffar you are the release manager for this.

Following commands in first line of a comment are recognized

• +1|approve[d]|sign[ed]: L1/L2's to approve it
• -1|reject[ed]: L1/L2's to reject it
• assign <category>[,<category>[,...]]: L1/L2's to request signatures from other categories
• unassign <category>[,<category>[,...]]: L1/L2's to remove signatures from other categories
• hold: L1/all L2's/release manager to mark it as on hold
• unhold: L1/user who put this PR on hold
• merge: L1/release managers to merge this request
• [@cmsbuild,] please test: L1/L2 and selected users to start jenkins tests
• [@cmsbuild,] please test with cms-sw/cmsdist#<PR>: L1/L2 and selected users to start jenkins tests using externals from cmsdist

[Dr15Jones]

Please change the name of the file to start with a lower case since this isn't a class header.

[wmtan]

Done.

[Dr15Jones]

+1

[Dr15Jones]

please test

[cmsbuild]

The tests are being triggered in jenkins.
https://cmssdt.cern.ch/jenkins/job/ib-any-integration/9876/console

[cmsbuild]

This pull request is fully signed and it will be integrated in one of the next CMSSW_8_0_X IBs after it passes the integration tests. This pull request requires discussion in the ORP meeting before it's merged. @slava77, @davidlange6, @Degano, @smuzaffar

[cmsbuild]

+1
Tested at: 23bbc79
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-12508/9872/summary.html

[cmsbuild]

This pull request is fully signed and it will be integrated in one of the next CMSSW_8_0_X IBs (tests are also fine). This pull request requires discussion in the ORP meeting before it's merged. @slava77, @davidlange6, @Degano, @smuzaffar

[cmsbuild]

+1
Tested at: c9d48c4
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-12508/9876/summary.html

[cmsbuild]

Comparison is ready
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-12508/9872/summary.html

[cmsbuild]

This pull request is fully signed and it will be integrated in one of the next CMSSW_8_0_X IBs (tests are also fine). This pull request requires discussion in the ORP meeting before it's merged. @slava77, @davidlange6, @Degano, @smuzaffar

[cmsbuild]

Comparison is ready
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-12508/9876/summary.html

[davidlange6]

+1
But this used to be a desirable thing NOT to do - lets discuss when I'm back