[opensuse-factory] Devel project <-> factory links
From reading all the stuff on the wiki I would expect at this point
I'm confused/have a dumb question: Suppose some package foobar is first created in a devel project. Life goes on, and then foobar gets submitted to factory and gets accepted. that the devel foobar should remain as before, and the new factory foobar would just contain a _link to the devel foobar... quoting: "Development, however, does not happen directly in openSUSE:Factory but in so called devel projects." But it looks like what actually happens is that the link goes the opposite way: the devel foobar is copied wholesale into factory, and then the devel foobar gets a _link pointing to the factory foobar (example: utilities/csvprintf). That seems backwards. E.g. suppose someone then BURP's the devel foobar. Now the devel foobar is different from the factory foobar. When and how does the factory foobar get updated? And when this happens, does the devel foobar get copied on top of the old factory foobar, and the devel foobar thrown away and recreated with a new _link? Would someone ever want to modify sources directly in the factory foobar, instead of the devel foobar? It seems like we now have two independent places you can make changes to a package. Instead, why doesn't it work this way: - The factory foobar has a _link that points to the devel foobar (possibly with a fixed revision) - Sources are never changed in the factory foobar directly - To update factory foobar, you just update the revision in the _link file. Sorry for asking such basic questions. Just trying to understand how this all works. Thanks, -Archie -- Archie L. Cobbs -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Mon, Feb 18, 2013 at 11:02:42AM -0600, Archie Cobbs wrote:
I'm confused/have a dumb question:
Suppose some package foobar is first created in a devel project. Life goes on, and then foobar gets submitted to factory and gets accepted.
From reading all the stuff on the wiki I would expect at this point that the devel foobar should remain as before, and the new factory foobar would just contain a _link to the devel foobar... quoting: "Development, however, does not happen directly in openSUSE:Factory but in so called devel projects."
But it looks like what actually happens is that the link goes the opposite way: the devel foobar is copied wholesale into factory, and then the devel foobar gets a _link pointing to the factory foobar (example: utilities/csvprintf). That seems backwards.
E.g. suppose someone then BURP's the devel foobar. Now the devel foobar is different from the factory foobar. When and how does the factory foobar get updated? And when this happens, does the devel foobar get copied on top of the old factory foobar, and the devel foobar thrown away and recreated with a new _link?
Would someone ever want to modify sources directly in the factory foobar, instead of the devel foobar?
It seems like we now have two independent places you can make changes to a package. Instead, why doesn't it work this way:
- The factory foobar has a _link that points to the devel foobar (possibly with a fixed revision) - Sources are never changed in the factory foobar directly - To update factory foobar, you just update the revision in the _link file.
Sorry for asking such basic questions. Just trying to understand how this all works.
This page explains stuff: https://en.opensuse.org/Build_Service/Collaboration You basically send a "submitrequest" from the development project towards Factory. This submitrequest follows by default the _link file. Once a Factory owner accepts it, the sources from the request get copied from the devel project to Factory. Also think of as: The development project package version is based on factory, and this "based on" is reflected by the link. Ciao, Marcus -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (2)
-
Archie Cobbs -
Marcus Meissner