Re: [Oneiric-Topic] LightDM for display management
Le mercredi 13 avril 2011 à 10:26 +1000, Robert Ancell a écrit : > Sure, there are definitely a number of required services. Note I'm not > ruling out running a GNOME session, it just depends if you can have a > cut down enough session to make it work. The services you require in a > login screen (basically power management, networking, audio) really are > all system services - I hope that GNOME is working towards taking these > things out of the session in the future. They're actually out of session for the most part: gnome-power-manager is merely talking to upower, nm-applet to NetworkManager, gnome-volume-control applet to pulseaudio (though which is per-session in Ubuntu IIRC). But you need something to display a GUI, you can't only rely on a system service. In GNOME 3, network and volume control are even handled directly from the Shell's process, and the GDM greeter could do the same. Also, if you want accessibility, you have to start a magnifier, a screenreader, or an on-screen keyboard per-session. So I don't think you can really be more lightweight than GDM *if* you want to implement all of these. You can consider they're not essential for most people and use a stripped-down DM, but you won't have those features. Tradeoffs... Cheers -- ubuntu-desktop mailing list ubuntu-desktop@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop
Re: [Oneiric-Topic] Packaging branches
Le mercredi 13 avril 2011 à 09:48 +0200, Martin Pitt a écrit : > usually I find it easier to get it from an upstream git diff. If > that's impractical, debdiffing the old against the new source works > too, of course. Hi, Right, I usually start a build of the new version and debdiff those while it's building -- Sebastien Bacher -- ubuntu-desktop mailing list ubuntu-desktop@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop
Re: [Oneiric-Topic] Packaging branches
Robert Ancell [2011-04-13 10:20 +1000]: > > * They come with quilt patches pre-applied in the source, which is > >not only horribly confusing and error prone, but also breaks > >merge-upstream pretty thoroughly. > I hadn't noticed that. The seems like absolutely the wrong behaviour. > Can this be fixed? I'm afraid it's called a feature :/ > Current method (perhaps I'm missing something here): > 1. Checkout bzr branch of debian/ directory Right, debcheckout -a packagename. > 2. Get tarball of current version (I use apt-get source, though you have > to be careful that it is the same version) > 3. Get tarball of latest version (I use bzr-buildpackage and then ctrl-C > once I have the tarball in the build-area/ directory) Not necessary, bzr bd-do or bzr bd -S do that for you. If the archive already has it, it gets it from there, otherwise it uses uscan to download it from upstream. > 4. Unpack tarballs somewhere manually > 5. Copy debian directory bzr bd-do does that. It puts you into a temporary dir with full source which you can work in, and if you exit 0, it copies back debian/ so that you can commit the changes. > 6. Diff two versions for changes (i.e. NEWS and configure.ac) - I use > meld here I usually don't need that for NEWS, as you can just grab the part which applies to the latest release. configure.ac is tricky indeed, usually I find it easier to get it from an upstream git diff. If that's impractical, debdiffing the old against the new source works too, of course. > 7. Update debian/rules debian/control etc > 8. Muck around with quilt/edit-patch to add/update/remove patches quilt push / edit stuff / quilt update etc. should be done in the bzr bd-do work tree. > 9. Copy back debian/ directory changes to bzr branch bzr bd-do does that when exit 0 Martin -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) -- ubuntu-desktop mailing list ubuntu-desktop@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop
