Linked by Thom Holwerda on Thu 28th May 2009 19:17 UTC
Permalink for comment 365869
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/22/13 22:23 UTC
Linked by Thom Holwerda on 05/22/13 13:38 UTC
Linked by Thom Holwerda on 05/22/13 13:30 UTC, submitted by JRepin
Linked by Thom Holwerda on 05/21/13 22:06 UTC
Linked by Thom Holwerda on 05/21/13 21:45 UTC
Linked by Thom Holwerda on 05/21/13 15:53 UTC
Linked by Thom Holwerda on 05/20/13 22:43 UTC
Linked by Thom Holwerda on 05/20/13 21:50 UTC
Linked by Thom Holwerda on 05/19/13 23:15 UTC
Linked by Thom Holwerda on 05/19/13 23:11 UTC, submitted by Drumhellar
More News »
Sponsored Links



Member since:
2009-02-19
I've only been a programmer for ~6 months: what I am about to say may be idiotic. But:
It is exactly as a programmer that the FHS annoys me. When I do the "configure, make, make install" (dance to install a dependancy, say), I have no idea where on my system the libraries I'm building are going to end up (yes, I know that I can usually specify that with configure, but, sometimes some things expect those libraries to be in their default locations: if I change that with configure, I may break some other library that has the library I'm building as a dependancy). When I'm writing a make file, it can be really, really annoying to figure out what my library include paths should be. If it was clearly specified and consistently enforced where libraries should go and where headers should go, my life would be a lot easier.