Am Dienstag, 19. Januar 2010 12:53:59 schrieb Vincent Untz:
Le mardi 19 janvier 2010, à 10:45 +0100, Stephan Kulow a écrit :
So what is a branch? It's a _link without diffs, the _link contains the revision of factory and additionally you have the full sources in the devel project. This means you can't easily find out from your osc checkout if the project made changes. Of course we can extend osc to store the md5 of the link target too, so you can adapt your scripts - but for now there is no such possibility from what I can see.
Is that problem enough to outweight the advantages?
I'll need to update some of my scripts, I guess, but that should be doable.
Can someone confirm that if I submit something from a branch to oS:F and it gets accepted, even if some oS:F checkin scripts changes a bit the .spec file, the branch will be updated to be the exact same content as oS:F?
The files as stored in the source server are not touched. But by default an "osc checkout" or "osc update" is merging both versions (to have the same what the build workers are using. And we want it merged by default to see the effects of it immediatly).
However, you can also decide to handle this manually. Please find more detailed informations on my blog posting: