Mailinglist Archive: opensuse-gnome (44 mails)
| < Previous | Next > |
Re: [opensuse-gnome] 2.19 Plan
- From: Gary Ekker <gekker@xxxxxxxxxx>
- Date: Mon, 23 Apr 2007 15:25:27 +0000
- Message-id: <1177341927.15511.0.camel@xxxxxxxxxx>
On Mon, 2007-04-23 at 16:09 +0100, James Ogley wrote:
> > For older we'll break, because new hal dependent stuff does not compile,
> > which causes breakage of many packages as a consequence (including gedit
> > in the chain). We may need to fix it or disable somehow a not supported
> > subset.
>
> G:S even as it stands now is very broken on 10.0 so I'd suggest we nuke
> that target anyway unless someone has the time to put into fixing it.
>
> The hal dependency affects 10.1 to a lesser degree as it stands with
> 2.16 in G:S - would it be possible to do one of the following?:
>
> a) Import that hal stuff into G:S and only build on 10.1 (I don't like
> this idea)
> b) Have a new project for hal which could then benefit anything else
> that needs it and change the target for 10.1 to use that project
> c) Nuke 10.1 as a target too (I don't like this one either)
>
> > And should we continue with 2.19 in Factory or continue there with 2.18?
> > What do you think?
>
> Will we get 2.20 in time for 10.3?
>
> I think I've suggested it before but maybe G:U could have a Factory
> target added so we (in this instance) stick with 2.18 in Factory so that
> we have a stable GNOME release in 10.3 and start building 2.19 in G:U.
> Then, once 10.3 is released, import the work from G:U into Factory and
> disable the Factory target on it until the next GNOME development cycle
> comes around.
That sounds like a good plan, at least until we know when 10.3 is going
to be released. I suspect we won't have time to get 2.20 in for 10.3.
-Gary
--
To unsubscribe, e-mail: opensuse-gnome+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-gnome+help@xxxxxxxxxxxx
> > For older we'll break, because new hal dependent stuff does not compile,
> > which causes breakage of many packages as a consequence (including gedit
> > in the chain). We may need to fix it or disable somehow a not supported
> > subset.
>
> G:S even as it stands now is very broken on 10.0 so I'd suggest we nuke
> that target anyway unless someone has the time to put into fixing it.
>
> The hal dependency affects 10.1 to a lesser degree as it stands with
> 2.16 in G:S - would it be possible to do one of the following?:
>
> a) Import that hal stuff into G:S and only build on 10.1 (I don't like
> this idea)
> b) Have a new project for hal which could then benefit anything else
> that needs it and change the target for 10.1 to use that project
> c) Nuke 10.1 as a target too (I don't like this one either)
>
> > And should we continue with 2.19 in Factory or continue there with 2.18?
> > What do you think?
>
> Will we get 2.20 in time for 10.3?
>
> I think I've suggested it before but maybe G:U could have a Factory
> target added so we (in this instance) stick with 2.18 in Factory so that
> we have a stable GNOME release in 10.3 and start building 2.19 in G:U.
> Then, once 10.3 is released, import the work from G:U into Factory and
> disable the Factory target on it until the next GNOME development cycle
> comes around.
That sounds like a good plan, at least until we know when 10.3 is going
to be released. I suspect we won't have time to get 2.20 in for 10.3.
-Gary
--
To unsubscribe, e-mail: opensuse-gnome+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-gnome+help@xxxxxxxxxxxx
| < Previous | Next > |