Linked by Andrew Hudson on Mon 20th Jun 2011 17:19 UTC
Permalink for comment 477864
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:
2005-11-15
There are many good reasons to have a package manager for Haiku. If you have ever installed one of the thousands of BeOS or Haiku apps from Haikuware you will find there are dependency challenges. Older BeOS apps need GCC2 libs to run correctly. Newer apps run with different GCC4 libs. And apps in development need a mix of other libs also in development. Currently there are several work-arounds, none of which are easy for the casual user.
You can download a 'big fat library install' with a bunch of libs all at a certain revision. This will work for some apps but breaks others. And when you install different apps, they too need different versions of the libs.
You can manage this manually with sym links, on an app-by-app basis. But it is a pain. And this is better done by automation.
Having a package manager is a really good idea for Haiku. For these reasons alone.
Edited 2011-06-20 18:33 UTC