Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

We ship a copy of bootstrap within our data files. They could just leave it as-is and have it working. Bootstrap is a CSS/JS library, there is no global /usr/lib to be concerned about.


> because it was built on top of Bootstrap 3, but Debian only shipped Bootstrap 2 at the time in a global package

> there is no global /usr/lib to be concerned about

Aside from possibly the path being different, which is of no concern, how can the 2 above sentences reconcile with each other?


It is trivial to make the Bootstrap 3 global package install into a different folder than Bootstrap 2. It isn’t so trivial for shared libraries without different sonames, for example.


Most of HN who've been around know what Bootstrap is (rip, old Twitter). The same rules apply whether your package dependencies are .css, .js or .so




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: