Hi,
At the moment, G:S:2.26 contains all the packages we have in G:F. I propose that we only keep there the packages for modules that follow the GNOME release cycle (and potential dependencies). This means we'd have a subset of the packages that live in G:F.
This should help for a few reasons:
+ gives us a better/clearer overview of what we maintain there + less work for the build service + less updates for users
If people like the idea, we can probably start by listing packages where the rdiff between openSUSE:11.1 and G:S:2.26 is empty.
Opinions?
Vincent
Vincent Untz wrote:
At the moment, G:S:2.26 contains all the packages we have in G:F. I propose that we only keep there the packages for modules that follow the GNOME release cycle (and potential dependencies). This means we'd have a subset of the packages that live in G:F.
I fully agree. You have just to think whether GTK+ should have a separate repository or not.
If people like the idea, we can probably start by listing packages where the rdiff between openSUSE:11.1 and G:S:2.26 is empty.
And reversely packages with version 2.26.x will become a part of G:S automatically.
I propose to move the rest to GNOME:APPLICATIONS or something similar. In difference to GNOME:Community it would be uses as a base for Factory.
On Fri, 2009-04-17 at 16:59 +0200, Stanislav Brabec wrote:
Vincent Untz wrote:
At the moment, G:S:2.26 contains all the packages we have in G:F. I propose that we only keep there the packages for modules that follow the GNOME release cycle (and potential dependencies). This means we'd have a subset of the packages that live in G:F.
I fully agree. You have just to think whether GTK+ should have a separate repository or not.
What would be the reason to put GTK+ in a separate repository?
If people like the idea, we can probably start by listing packages where the rdiff between openSUSE:11.1 and G:S:2.26 is empty.
And reversely packages with version 2.26.x will become a part of G:S automatically.
I propose to move the rest to GNOME:APPLICATIONS or something similar. In difference to GNOME:Community it would be uses as a base for Factory.
Do you mean something like GNOME:Apps:2.26, GNOME:Apps:2.28 etc?
Cheers, Magnus
Magnus Boman wrote:
On Fri, 2009-04-17 at 16:59 +0200, Stanislav Brabec wrote:
I fully agree. You have just to think whether GTK+ should have a separate repository or not.
What would be the reason to put GTK+ in a separate repository?
For projects, that depend just only on the latest GTK+. But it is probably overkill.
If people like the idea, we can probably start by listing packages where the rdiff between openSUSE:11.1 and G:S:2.26 is empty.
And reversely packages with version 2.26.x will become a part of G:S automatically.
I propose to move the rest to GNOME:APPLICATIONS or something similar. In difference to GNOME:Community it would be uses as a base for Factory.
Do you mean something like GNOME:Apps:2.26, GNOME:Apps:2.28 etc?
No. I think about a single repository to prevent multiple copies of the same binary.
These packages don't follow GNOME release cycle and most of them don't depend on the latest GNOME version => there is no reason to split them per GNOME version.
On Fri, Apr 17, 2009 at 20:06, Vincent Untz vuntz@opensuse.org wrote:
If people like the idea, we can probably start by listing packages where the rdiff between openSUSE:11.1 and G:S:2.26 is empty.
except for the ones we decided not to update (gnome-bt, gnome-phone-manager...) don't we have an update for everything else? :-)
If indeed there is such a package (same in oS 11.1 and G:S:2.26), we should definitely drop it from the GNOME repo..
-Suman
On Sat, 2009-04-18 at 01:46 +0530, Suman Manjunath wrote:
On Fri, Apr 17, 2009 at 20:06, Vincent Untz vuntz@opensuse.org wrote:
If people like the idea, we can probably start by listing packages where the rdiff between openSUSE:11.1 and G:S:2.26 is empty.
except for the ones we decided not to update (gnome-bt, gnome-phone-manager...) don't we have an update for everything else? :-)
If indeed there is such a package (same in oS 11.1 and G:S:2.26), we should definitely drop it from the GNOME repo..
The only problem with this is that we wouldn't know then if the package needs to be updated (osc gnome t --project=GNOME:STABLE:2.26). And even for gnome-bt etc, we would probably want to keep track of minor version updates and try to keep them up to date.
If osc gnome can work without having these non updated packages, then sure, lets get rid of them.
Cheers, Magnus
On Sat, Apr 25, 2009 at 07:07, Magnus Boman captain.magnus@gmail.com wrote:
On Sat, 2009-04-18 at 01:46 +0530, Suman Manjunath wrote:
On Fri, Apr 17, 2009 at 20:06, Vincent Untz vuntz@opensuse.org wrote:
If people like the idea, we can probably start by listing packages where the rdiff between openSUSE:11.1 and G:S:2.26 is empty.
except for the ones we decided not to update (gnome-bt, gnome-phone-manager...) don't we have an update for everything else? :-)
If indeed there is such a package (same in oS 11.1 and G:S:2.26), we should definitely drop it from the GNOME repo..
The only problem with this is that we wouldn't know then if the package needs to be updated (osc gnome t --project=GNOME:STABLE:2.26).
Sounds like the database can do with one more field for all the packages. A field which says "disable update-lookup for this package".
And even for gnome-bt etc, we would probably want to keep track of minor version updates and try to keep them up to date.
The probability of a stable 2.24.x release after a 2.26.0 release ~ 0 So, would we really miss out on a stable update? Even if there is such a release, we could always do it if the community needs it.
-Suman
On Fri, 2009-04-17 at 16:36 +0200, Vincent Untz wrote:
Hi,
At the moment, G:S:2.26 contains all the packages we have in G:F. I propose that we only keep there the packages for modules that follow the GNOME release cycle (and potential dependencies). This means we'd have a subset of the packages that live in G:F.
This should help for a few reasons:
- gives us a better/clearer overview of what we maintain there
- less work for the build service
- less updates for users
If people like the idea, we can probably start by listing packages where the rdiff between openSUSE:11.1 and G:S:2.26 is empty.
Opinions?
See my reply to Suman.
Cheers, Magnus
-
Magnus Boman -
Stanislav Brabec -
Suman Manjunath -
Vincent Untz