Le vendredi 17 septembre 2010 à 14:29 +0100, Anas Nashif a écrit : > Packages having the same name and residing in different repos should > not be a problem, since the package manager can deal with same package > name from two different vendors.
This answer might be outside the subject scope, but the comment is not correct. Many packages have features that can be turned on or off at build time. If you may have a newer version of the library in a different repository that does not support some feature you nead, then you program won't work (usually resulting in a dynamic link error). But, as mention earlier, this can be solved by having policies on where your level of compliance let you install your library (e.g. using /opt/repo/), and by having RPATH being set properly into your repository executables. This would make the packaging task slightly harder, but seems reasonable solution. With time, repository owner will file ticket and vote to get those common libraries included in the Core (or Handset, Notebook, etc). This would be one of the way to contribute to Meego. Also don't read me wrong, included does not mean installed by default. cheer, Nicolas
_______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
