Linked by Amjith Ramanujam on Fri 8th Aug 2008 03:58 UTC
Thread beginning with comment 326191
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.




Member since:
2006-01-04
Unfortunately, sometimes the odd dependency gets in there without you realising you're depending on it.

Even more confusing can be libraries that that can have different features/sub-dependencies depending on what options it was compiled with. Some libraries I have used even install different headers depending what how you compiled them.
Every piece of software has a certain set of assumptions about the end-users computer (e.g. sh is installed is a fair assumption), but sometimes one mistakenly makes the wrong assumption: "I thought that was present on every system" type assumptions. Often it's best to create a chroot build environment only containing your expected dependencies built with the most minimal features, just to test it.
Of course, the every once in a while I think developers expect you to read the source code yourself and work out the dependencies