Dne 14.3.2013 12:48, Pierre-Yves Chibon napsal(a):
On Thu, 2013-03-14 at 12:42 +0100, Vít Ondruch wrote:
And we are speaking about possible changes in RPM, that might affect all packages in Fedora.
But since you do various branches in one .spec file, the .spec file becomes un-updatable by script.
Which in some case might not be a bad thing. The other question is, is it really so important to fix all the packages? Or should we just invite the package to clean up the spec when they update their package?
Yes, the possibility to be able to modify .spec file by scrip is crucial. Not every change in packaging guidelines is pure aesthatical issue. If you bump ruby(abi) or so, you have to update all packages which depends on it. If you have several ruby(abi)s in several brachnes, then you have no other option then do it manually or keep it broken. Note that there is also plenty of packages which are more or less unmaintained. If I don't do that by script, nobody will do that. Although they are unmaintained, it doesn't mean they could be dropped.
And btw, we got rid of versioned ruby(abi), hopefully forever. There should be no need to script in in future.
The current system allows each maintainer to use the latest version of the guidelines or to maintain one spec consistent across branches if he wishes to. I think this is the approach that has the most flexibility and changing it will crease some feathers.
As well as non-changing it. If beginer takes a look on some hugely conditionalized .spec file, he will screaming escape. .spec file should be sort of configuration file, not a script.
I agree, like I say, there is a point where having different spec per branch is a good thing (even a necessity), but I think this point should be left to the packager to decide.
It would be nice if such .spec files could be automatically recognized at least. Or it it would be somewhere in fedpkg or so.
Anyway, I think I've expressed what I wanted to say, so I'll try not to run in circles :)
Agree
Vít