Commen=
t # 11
on bug 98964<=
/a>
from Emil Velikov
(In reply to Zolt=C3=A1n B=C3=B6sz=C3=B6rm=C3=A9nyi from comment #9)
> Although the OS is Yocto, the Mesa recipe is mos=
tly mine including the patch
> to revert this horrible idea of hard links. Hard links are good until =
you
> package the drivers into separate subpackages as it breaks the hard li=
nks
> and creates separate files instead. I saved more than 50MB on a 2GB di=
sk
> which is substantial for an embedded system where we need the disk spa=
ce but
> it is very constrained.
>=20
> Haven't seen any ill effect on our systems because of it. We use only =
single
> GPU machines, so it shouldn't make a difference in behaviour. Perhaps =
with
> PRIME it would but we don't use it.
I'm getting really off topic with this:
Above all: yes using hard links is nasty.
If you're having a single (or multiple fixed) GPU system then building mult=
iple
drivers is a _very_ bad idea. If you're doing that for embedded systems the=
n it
gets even worse. Thus having separate $driver subpackages makes no sense :-(
Using symlinks is brittle (not PRIME related). So you really don't want to =
ship
something based on it.
</offtopic>