search

ucberkeley / bce

Berkeley Common Environment provides a common Linux computational environment for classwork and research.
Apache License 2.0
13 stars 6 forks source link

MRAN date based on build day #57

Open ck37 opened 9 years ago

ck37 commented 9 years ago

Should the MRAN repo be based on the current day that the build is being created, rather than being hardcoded? Or find the most recent MRAN archive to use? http://mran.revolutionanalytics.com/

It seems kind of unfortunate to have to update the URL whenever building or otherwise having packages potentially worth upgrading immediately after the build is created. E.g. right now the MRAN is 2.5 months old.

ryanlovett commented 9 years ago

It should be set to a particular day for reproducability. The day of the build would work.

Ryan

On Thu, Jul 23, 2015 at 10:03 PM, Chris Kennedy notifications@github.com wrote:

Should the MRAN repo be based on the current day that the build is being created, rather than being hardcoded? Or find the most recent MRAN archive to use? http://mran.revolutionanalytics.com/

It seems kind of unfortunate to have to update the URL whenever building or otherwise having packages potentially worth upgrading immediately after the build is created. E.g. right now the MRAN is 2.5 months old.

— Reply to this email directly or view it on GitHub https://github.com/ucberkeley/bce/issues/57.

ck37 commented 9 years ago

Right, for the "most recent MRAN" option it would still be hardcoded in the actual AMI, but it would handle the contingency that there may not be an MRAN folder for the day of the build for whatever random reason.