no external panels for gnome-control-center [was Re: GNOME Feature Proposal: Backup]
On Tue, 2011-05-10 at 20:51 +0100, Bastien Nocera wrote: On Tue, 2011-05-10 at 15:49 +0200, Michael Terry wrote: Hello! You may remember me as the bloke that proposed the Déjà Dup backup tool as a GNOME module a little back, right as modules were being reorganized. I've been encouraged to try again as a Feature. I don't fully understand the process, but I gather an email to this list starts it off. Here's a quick thousand foot view: * Homepage here: https://launchpad.net/deja-dup * It's a backup program aimed at non-technical users. * It's a graphical wrapper and policy manager for the backup program duplicity. * It's included by default in Fedora 13 on and will be default in Ubuntu 11.10. * It follows the GNOME schedule and best practices already. For the next major version (20.0), I've done a redesign aimed at making it more invisible and appear as part of the OS. I've made it live just as a control center panel and removed some branding to look a bit less like a separate app. See http://live.gnome.org/DejaDup/Screenshots/Future for screenshots. Déjà Dup 19.1, which includes those changes, is already in Fedora Rawhide and will be in Ubuntu Oneiric once we land the GNOME 3 control center. That won't work for long. Once we've move the Bluetooth panel directly in the control-center, we'll be removing the external API from the control-center. It was only added for gnome-bluetooth, and will be removed then as well. Because people carried on using the API despite being told it was going away, the GNOME control-center library isn't exported any more in master. That doesn't mean that the functionality shouldn't be in the control-center, but the integration needs to be even better within GNOME for us to add it there, including design, competitive research, etc. snip ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Some jhbuild changes (past and future planned)
Hi, Some developers might have noticed that I've been making some changes in jhbuild this cycle. Why? So I spend less time staring at other people's build pastebins. At a very high level, my main goals are: * Improve the ability to do partial builds * Try very hard to avoid unobvious build failures An example of an unobvious build failure is stale files in the buildroot, left over from when a module installed a file at one point, then stopped, or moved it. Then you might be linking to an old, no longer built copy of a library, which can create *very* confusing issues. To work towards this, jhbuild now uses make install DESTDIR= just like most distributions do, and generates a manifest at build time. All decent build systems (autotools, waf, distutils) support this, so it has been mostly transparent. I've tried to be responsive and fix problems quickly as I see them, but some like https://bugzilla.gnome.org/show_bug.cgi?id=654592 crop up in things I may not happen to build. If you catch me on IRC, I should be able to help. Or you can file a bug. Future changes you should be aware of: srcdir != builddir by default https://bugzilla.gnome.org/show_bug.cgi?id=652475 Basically, if your module doesn't support this currently, please make it do so. parallel make https://bugzilla.gnome.org/show_bug.cgi?id=654686 It's really not too hard to maintain if the developers active on a project use it consistently, so just start doing it now. (Or, add the .NOTPARALLEL flag if you just don't care) ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
