ext Attila Csipa <me...@csipa.in.rs> writes: > There are several points that need to be addressed if you are sharing > components/engines/etc
Sure, there are all kinds of 'interesting' consequences, and they are worth exploring by those who are daring enough and want to reap the benefits. It is of course easier not to require non-standard packages, so if you think it is a bad idea, just don't do it. I'd mostly wanted to make the point that we should not categorically forbid it, and keep the issue on the table. People will do it anyway. > Now, before someone misunderstands this as an argument NOT to allow > dependencies on 3rd party packages - the whole point is IF you have a > shared repository, you must have a procedure/agreement of how you > update /modify/publish stuff there in order to prevent it from > becoming a jungle/huge pile of unsolvable intertwined dependencies. Yes, and that's what we are doing in MeeGo, no? _______________________________________________ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
