On Sun, Nov 28, 2010 at 10:15 PM, Arjan van de Ven <[email protected]> wrote: > On 11/28/2010 12:13 PM, Alexander Kanevskiy wrote: >> >> On Sun, Nov 28, 2010 at 6:25 PM, Arjan van de Ven<[email protected]> >> wrote: >>> >>> On 11/28/2010 8:14 AM, Alexander Kanevskiy wrote: >>>> >>>> On Sun, Nov 28, 2010 at 6:12 PM, Arjan van de Ven<[email protected]> >>>> wrote: >>>>> >>>>> On 11/28/2010 6:59 AM, Zhu, Peter J wrote: >>>>>> >>>>>> It’s not used by any verticals or included in any pkg groups. >>>>>> >>>>>> Please let us know if there are objections... >>>>>> >>>>> which bug is there in the package that warrants removing it? >>>>> (I understand that fixing unused packages might be too much work for >>>>> their >>>>> worth... >>>>> but if there's no bugs ........ >>>>> ) >>>> >>>> A bit different question: where is MeeGo Architecture Forum decision >>>> about removing some packages ? >>> >>> there is no decision to delete packages like this, and I'm pretty sure >>> there >>> won't be one; >>> I for sure will be against it... esp for packages that have no serious >>> maintenance burden. >> >> Well, it's not question of who for or against removal. >> >> My point was that all packages that we have in MeeGo should have clear >> owner/maintainer and clear understanding and description where this >> package fits to architecture of MeeGo. So any addition or removal of >> packages should go trough process of FEA# and reviewal of Business >> people and Architects Forum to give a decision either this package >> present or not present in MeeGo. It shouldn't be anarchy of adding or >> removing packages. > > agreed. > > I would also like to point out that I consider this a point for adding a > package to an image, > more than having a package in OBS at all. > For the later we should be *much* more liberal in having packages than we > should be for the former!
Having package in OBS, means package has owner/maintainer. We have many package which doesn't have clear owner and clear idea why it's present. Due to that, we might have accidents when some other applications would be linked against not-so-maintained libraries. Or spontaneous upgrades of such not-so-maintained packages where nobody would be able to say why this upgrade was happen. Also, in case of not maintained packages, in case of build breaks - who going to look at those ? Plus, if it's not maintained and not used in images - what's the point of keeping it in OBS and on all mirrors ? Let's move to Community OBS if somebody from community would like to maintain it. If it would be no volunteers of maintaining package in community OBS, drop it completely. PS. We clearly need good process which would describe adding/removing/moving-to-community/dropping-completely activities with packages :( -- br, Alexander Kanevskiy _______________________________________________ MeeGo-packaging mailing list [email protected] http://lists.meego.com/listinfo/meego-packaging
