Le vendredi 24 juin 2011 02:09:55, Michael Scherer a écrit : > - a packager decide to do it. Based on the policy ( outlined in another > mail ), and maybe seeing with the maintainer first about that for non > trivial applications, the backport can be done, or not. The criterias > for being backported or not are not important to the process, just > assume that they exist for now ( and look at next mail ). So based on > criteria, someone say "it can be backported, so I do it". > > - I am not sure on this part, but basically, we have 2 choices : > - the packager take the cauldron package and push to backport testing > - the packager move the cauldron package in svn to backport, and there > send it to backport testing. > > Proposal 1 mean less work duplication, but proposal 2 let us do more > customization. >
If we want to be able to set stricted requires between backports to allow safe cherry-picking, is it OK to do it in cauldron without any side effects ? Or should we change the spec file only in the backport branch of the package (which then would mean option 2) ? Best regards Samuel Verschelde
