Am Dienstag, 6. April 2010 10:35:26 schrieb Karsten König:
I see two ways of fixing the problem, and they both require certain
overhead. Either the package in Backports will have build/publish disabled for the time there is a beta in KKFD/o:F, or the package in Backports will be a branch instead of a link and will need manual updates. In both cases the overhead is small, but in the first case people doing updates in KKFD need not to forget to do it, otherwise a beta gets into Backports, in the second case somebody needs to remember to do the update as necessary.
I'd prefer the second option, it's safer and in the usual case it's no
rocket science, so it can be done by anybody. It probably could be even scripted to make it even easier. Would be somebody willing to keep an eye on it?
Does the webinterface rework include a version compare between projects? Otherwise it could propable be done easily as a script with osc yes. I would be willing to try it on a few packages first, I'd start with a script that checks the .spec files for versions, is there a policy for unstable package versioning? Looking for alpha, beta, rc and svn/git is simple, otherwise > .50 ? How to manage stuff like k3b which will remain "beta" for quite longer, make a white list?
darix in opensuse-buildservice just pointed out another way to do this, the _link supports revisions, so we could just update the _link when the update should be forwarded to :Backports
JFYI, there is "osc linkpac -c" to create a link to the current revisions and you can update the revsion with "osc setlinkrev". -- Adrian Schroeter SUSE Linux Products GmbH email: adrian@suse.de -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org