Hi, > -----Original Message----- > From: Boudra Fathi (Nokia-MS/Helsinki) > Sent: Thursday, March 31, 2011 6:12 PM > To: Zabaluev Mikhail (Nokia-MS/Helsinki); [email protected] > Cc: [email protected] > Subject: RE: [meego-packaging] Dropping yaml > > > > did you miss the part where once a package is using yaml, you > should > > > keep doing so ? > > > > In fact, I did. Could you point me at the stated policy to this > effect? > > Topic visited 8 months ago: http://lists.meego.com/pipermail/meego- > packaging/2010-July/000579.html > It has been agreed by the RMs/architect
What exactly has been agreed? This message from Anas reflects my case exactly: http://lists.meego.com/pipermail/meego-packaging/2010-July/000586.html - packager should not change packaging format randomly. - You need to be the main maintainer - You need to have a valid reason why not to use the yaml format I have sent requests to become the bugowner for the packages involved (is it still equivalent to the maintainer?), since the previous maintainers were doing it on our request and have since gone on to other tasks. Those requests are not approved yet, maybe this is the problem. I have two reasons to not use the yaml format: 1. The spectacle format and tools present a learning curve for me, while the RPM spec format does not. On a more subjective note, I see in Spectacle an unnecessary layer obscuring the actual package specification. 1.1. The tools are either outdated or not easily available for installation. The quality of diagnostic messages is offputting as well (no, the cited fix did not improve much). 2. I want to be able to easily import changes in packaging from other distributions, or even an OBS upstream such as this one: https://build.opensuse.org/package/show?package=telepathy-qt4&project=KDE%3AUnstable%3APlayground Best regards, Mikhail _______________________________________________ MeeGo-packaging mailing list [email protected] http://lists.meego.com/listinfo/meego-packaging
