{var%20f='http://v.t.sina.com.cn/share/share.php?appkey=1515056452',u=z||d.location,p=['&url=',e(u),'&title=',e(t||d.title),'&source=',e(r),'&sourceUrl=',e(l),'&content=',c||'gb2312','&pic=',e(p||'')].join('');function%20a(){if(!window.open([f,p].join(''),'mb',['toolbar=0,status=0,resizable=1,width=440,height=430,left=',(s.width-440)/2,',top=',(s.height-430)/2].join('')))u.href=[f,p].join('');};if(/Firefox/.test(navigator.userAgent))setTimeout(a,0);else%20a();})(screen,document,encodeURIComponent,'','','https://www.manongdao.com/data/attach/logo/logo.png', '推荐 放荡不羁爱自由 的问题《how to prevent bundler from adding platform info t》','https://www.manongdao.com/q-685959.html','页面编码gb2312|utf-8默认gb2312'));){kind=link}
every time I run bundle --without=production bundler adds platform information PLATFORMS
x86-mingw32 to Gemfile.lock and I have to remove that info manually as I am deploying to Heroku. If I do not remove it, Gemfile.lock is not added to repository and causes errors.
how can I prevent bundler from adding platform info to Gemfile.lock
I had a very similar question - Can I stop Bundler from adding RUBY VERSION to Gemfile.lock - and it turns out the answer is that it can't be done. Bundler adds this information within the
to_lockmethod and there's no conditional to skip that section.It seems like it would be possible to refactor
to_lockto control which sections of the lockfile are actually written, but so far this hasn't been enough of a pain point for me to make that effort yet.