[prev in list] [next in list] [prev in thread] [next in thread] 

List:       fedora-devel-list
Subject:    Re: BlueZ Status in Fedora.
From:       Adam Williamson <awilliam () redhat ! com>
Date:       2013-08-17 0:19:27
Message-ID: 1376698767.23417.1.camel () adam
[Download RAW message or body]

On Thu, 2013-08-15 at 15:10 -0700, Dan Mashal wrote:
> On Thu, Aug 15, 2013 at 3:04 PM, Dan Mashal <dan.mashal@gmail.com> wrote:
> > On Thu, Aug 15, 2013 at 10:55 AM, Lars Seipel <lars.seipel@gmail.com> wrote:
> >> On Wed, Aug 14, 2013 at 08:37:19PM -0700, Dan Mashal wrote:
> >>> Otherwise we are looking at possibly reforking gnome-bluetooth at this
> >>> point in time.
> >>
> >> Reforking? And then wait until the bitrot sets in again? ;-)
> >>
> >> Can't you just use gnome-bluetooth proper and resurrect the panel icon
> >> stuff like Kalev proposed?
> >
> > Not so simple as reverting a commit. Must discuss with upstream.
> >
> > Dan
> 
> 
> Also as Wolfgang (comaintainer for MATE) said and I personally would
> like to reiterate:
> 
> "3. Also runtime dependencies needs to be checked, we don't want to be
> install more gnome as necessary in mate."
> 
> The whole point of forking to be dependant on gnome upstream as little
> as possible.

If you want to be independent of GNOME upstream, you need the resources
to keep up to date with upstream changes in a timely fashion. It's not
going to work for Fedora to delay moving to new upstream releases of
major components for entire release cycles because MATE didn't have the
resources to be ready for the change.
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora
http://www.happyassassin.net

-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
[prev in list] [next in list] [prev in thread] [next in thread]