Issue 657: Record BlibBuild command-line arguments in LibInfo table

issues
Status:open
Assigned To:matt.chambers42@gmail.com
Type:Defect
Area:Skyline
Priority:3
Milestone:19.2
Opened:2019-06-19 by Brendan MacLean
Changed:2019-06-19 by Brendan MacLean
Resolved:
Resolution:
Closed:
2019-06-19 Brendan MacLean
Title»Record BlibBuild command-line arguments in LibInfo table
Assigned ToGuest»matt.chambers42@gmail.com
Type»Defect
Area»Skyline
Priority»3
Milestone»19.2
A while back now, we added the cut-off scores to the SpectrumSourceFiles table to improve our ability to reproduce creating a .blib file. This should definitely help if the file was built with a Skyline release, since that release if fairly well controlled, and the user records which Skyline release it was.

Hmmm... It would really be nice to record more information about how a library was built, including at least the exact command-line arguments (potentially multiple rows, since a redundant .blib file can be written two multiple times). And also better version information about the version of BlibBuild and/or Skyline that built the library.

We should feel more confident that someone can start from a found .blib file and reproduce it exactly. The recent addition of the search files to SpectrumSourceFiles also helps with this, but we are still missing information.