Hi, > -----Original Message----- > From: ext Arjan van de Ven [mailto:[email protected]] > Sent: Thursday, March 31, 2011 4:45 PM > To: Zabaluev Mikhail (Nokia-MS/Helsinki) > Cc: [email protected]; [email protected] > Subject: Re: [meego-packaging] Dropping yaml > > > Trouble is, I did not touch that spec at all. > > Surely there should be a way to make spectacle completely overwrite > the spec without trying to be smart about patching it? Or is it so that > you can't actually express everything in yaml, so the users are advised > to descend into a generate-and-hack extravaganza with valuable > information spread between the two files? > > > > And the main issue remains: I don't want to grapple with Spectacle > yaml syntax, when I already know what to do in the spec. For example, I > knew immediately how to add %exclude directives to the file list, while > with yaml it would have taken me a while to figure it out. MeeGo should > be a friendly environment to all kinds of maintainers, including > experienced ones, right? > > you can express everything in the yaml. > autospectacle does exactly that,
$ apt-cache search autospectacle $ Another hurdle. I have already added the repository hosting MeeGo tools. The Wiki search does not find anything on using it, either. > create a full yaml that is sufficient > to generate a complete and final spec. The main question still stands: why should I be slowed down with these extra artifacts? If I suddenly abandon my packages, I'm sure the RPM newbie that comes after me will be able to use those great tools to convert everything back to the suitable layering of obscure syntax, no? As my current revision in devel:telepathy is, I can easily port packaging changes from Fedora or other RPM-based distributions, should the need arise. The wiki page on packaging guidelines (http://wiki.meego.com/Packaging/Guidelines) currently states: * It is NOT mandatory to use spectacle. Please tell the people in charge of accepting package requests to not impose seemingly counter-official policies without a good reason. This discourages contribution to MeeGo. Right now, we have a critical bug on our hands that I'm unable to fix as quickly as I could, because of the obstruction: https://bugs.meego.com/show_bug.cgi?id=13291 Best regards, Mikhail _______________________________________________ MeeGo-packaging mailing list [email protected] http://lists.meego.com/listinfo/meego-packaging
