You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Ryan and I spoke earlier, and here are a few setup improvements that we'll be making:
conf files will be split by package, e.g. rather than install conf we'll have boost.conf, bullet.conf and jsoncpp.conf.
If a user is found to have an install.conf it'll notify them of the change so users who update their existing builds won't be left with cryptic error messages once the change is pushed.
Additionally, it will also include the integrity checks Drew suggested in issue #3. It will deviate from Drew's recommendation in one way though: the hash will be specified in the conf, rather than being grabbed from a remote server. This is mainly to ease installation in the case of packages already being located locally.
The text was updated successfully, but these errors were encountered:
Refactoring of the conf files is now complete. The only thing that remains to be completed is SHA1 hash verification. File hashes and sha1sum path configuration parameters are already included in the conf files, but they don't do anything currently. This was done to avoid requiring yet another conf re-generation when hash verification is implemented.
Ryan and I spoke earlier, and here are a few setup improvements that we'll be making:
conf files will be split by package, e.g. rather than install conf we'll have boost.conf, bullet.conf and jsoncpp.conf.
If a user is found to have an install.conf it'll notify them of the change so users who update their existing builds won't be left with cryptic error messages once the change is pushed.
Additionally, it will also include the integrity checks Drew suggested in issue #3. It will deviate from Drew's recommendation in one way though: the hash will be specified in the conf, rather than being grabbed from a remote server. This is mainly to ease installation in the case of packages already being located locally.
The text was updated successfully, but these errors were encountered: