On Fri, Aug 16, 2013 at 4:27 AM, Mike Hommey <m...@glandium.org> wrote:
> > - Remove all conditional feature configuration from configure. > > WebRTC et al are always on. Features should be disabled dynamically > > (prefs), if at all. > > - Reduce configure settings to choice of OS and release or developer. > > With my Debian hat on, let me say this is both x86/x86-64/arm and > Firefox/Firefox-OS centric. > I understand that you see that as a negative, but I see that as a big positive because it maximizes the benefit:cost ratio of platform support. > There are features that don't build on non mainstream architectures (hey > webrtc, i'm looking at you), and while I do understand the horror it can > be to some people that there could be a Firefox (^WIceweasel) build that > doesn't support all the web, it's still better to have a browser that > doesn't support everything than no browser at all (and considering i get > bug reports from people using or trying to use iceweasel on e.g ppc or > ia64, yes, there *are* people out there that like or would like to have > a working browser, even if it doesn't make coffee). > > And Gecko is not used only to build web browsers (for how long?), so it > makes sense for some features to be disableable at build time. > If it helps at all, I'd be happy for us to stop trying to support any (product, target platform, build platform, toolchain) combination in mozilla-central that isn't (planned to be) used in a normal mozilla-central TBPL run: https://tbpl.mozilla.org/. Cheers, Brian _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
