View Single Post
Posts: 3,319 | Thanked: 5,610 times | Joined on Aug 2008 @ Finland
#6
Originally Posted by vivainio View Post
Well, as it is these applications need to graduate to the Nokia repository (where e.g. Qt Mobility sits ATM). This will kill normal evolution of the package on extras side, so if the package will continue evolving the "extras" instance of the package needs to be renamed to -experimental or somesuch and the library files installed in a different directory.
Agreed. We already did this the hard way with libqt4-maemo5, were lucky enough to spot and react in time with regard to the Web Runtime, but it could be beneficial if we could make that into a policy (it's a sort-of-recommendation now).

What we need is a process how we choose what packages we will "bless" to the nokia repository, and when. If it's currently just a handful of packages, we can go through an accelerated "special case" process and request this from the guy that has the power to do this. If we need an ongoing process, Community Council may be the instance that could request packages to be promoted there every now and then.
Yes ! That is exactly what I'm talking about - we already had complaints people getting turned down from Ovi because of this - now, the thing is that we from *here* do not know which libraries are needed for people wanting to go through Ovi. That's why we feel we need a less ad-hoc process (ideally, get a report of the most requested Extras packages because of which Ovi acceptance failed, or a clear Q&A point in Ovi that tells people that they can come to us and at least ASK for a certain package they might need - and then we can see who is the maintainer, if that is a 'Nokian' package or not, whether it is feasible to push it to the blessed repos down the line, etc, etc).
__________________
Blogging about mobile linux - The Penguin Moves!
Maintainer of PyQt (see introduction and docs), AppWatch, QuickBrownFox, etc
 

The Following 2 Users Say Thank You to attila77 For This Useful Post: