On 31 Mar 2011, at 16:53, <[email protected]> <[email protected]> wrote:
> 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. How does it obscure the package specification? Does it generate something not according to the "standard"? What does it do wrong? If you package for meego, you need to spend some time "learning" and there is really not much to it. If you do not like it, then fine, that is acceptable, not everybody likes it and I know it does not provide an answer for everything, but instead of spending a few minutes learning how things are being done, you chose to ridicule the english in the tool. > 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). Nobody is perfect and english is not the native language of everyone who works on meego and that is not a reason good enough not to use a tool. Your comments are valid and should be taken seriously (for example it would help if you report bugs against the above if it is not fixed already) but again, this is not a reason to not use the tool > 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 One of the reasons we introduced spectacle was exactly to avoid this, there is not much in this package to have us copy stuff from other distros, it is really a simple case for packaging and thats why it works well with spectacle. Both reasons are not good enough for changing packaging of such a simple piece of software, really. Anas > > Best regards, > Mikhail _______________________________________________ MeeGo-packaging mailing list [email protected] http://lists.meego.com/listinfo/meego-packaging
