josch1337

5 ms·

1.
AI War II Is Now on Kickstarter(kickstarter.com)
4 points by josch1337 10y ago|0 comments
2.
Star Trek: Renegades Episodes 2 and 3 Kickstarter(kickstarter.com)
2 points by josch1337 11y ago|0 comments
3.
by josch1337 11y ago
here is another thing: Instead of using debootstrap to create your chroot environment, try using multistrap. Multistrap uses apt to do package selection and not the "stupid" dependency resolver that debootstrap uses. Thus, you hav
4.
by josch1337 11y ago
I don't know how big the strongly connected component has to become so that you might call bootstrapping Debian "nearly impossible" but last year there were just two new Debian ports: arm64 and ppc64el. So apparently it is st
5.
by josch1337 11y ago
On top of what somerandomone said (which is already correct) imagine you have source packages A, B, C and D which depend on each other through the binary packages they build and the binary packages they build depend on like this: A->B-&g
6.
by josch1337 11y ago
The purpose is, to have a somehow quantifiable measure how hard it becomes to bootstrap Debian. Because the larger the central strongly connected component, the more software is involved in the bootstrap process and has to either be cross c
7.
by josch1337 11y ago
you might be interested in following this thread: http://lists.debian.org/87r3qurhhm.fsf@deep-thought.43-1.org
8.
by josch1337 11y ago
The larger that component is, the more work is needed to make it acyclic (to derive a linear build order). Ideally this "work" is done automatically but for that, more meta data has to be added. In Debian, source package dependenc