Re: Indicator applets and related packages
- To: Evgeni Golov <firstname.lastname@example.org>
- Cc: email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com
- Subject: Re: Indicator applets and related packages
- From: Raphael Hertzog <firstname.lastname@example.org>
- Date: Mon, 14 Jun 2010 12:14:37 +0200
- Message-id: <20100614101437.GB26563@rivendell>
- Mail-followup-to: Evgeni Golov <email@example.com>, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org
- In-reply-to: <20100614093259.GA9570@dorei.kerker.die-welt.net>
- References: <20100614073602.GA25691@rivendell> <20100614093259.GA9570@dorei.kerker.die-welt.net>
On Mon, 14 Jun 2010, Evgeni Golov wrote:
> I'd like too, thus I packaged libindicator (sid) and
> xfce4-indicator-plugin (NEW) :)
I saw libindicator and wondered why indicator-applet was not in the same
batch and investigated and found your RFP and this led me to this mail.
> > The missing source packages are AFAIK:
> > - libdbusmenu https://launchpad.net/ubuntu/+source/libdbusmenu
> > (no RFP/ITP known)
> > - libindicate https://launchpad.net/ubuntu/+source/libindicate
> > RFP: http://bugs.debian.org/560122
> Interested in those, planing to package, will contact ITP-author.
They are build-dependencies of several other source packages, so when do
you expect to have a first version ready to test ? :-)
> > - indicator-applet https://launchpad.net/ubuntu/+source/indicator-applet
> > RFP: http://bugs.debian.org/534556
> No GNOME here, no way to test, sorry.
Is that really the only component depending on Gnome?
> > I hope we can find maintainers for all those. Should they be maintained
> > within the Debian Gnome team ?
> libindicator is currently collab-maint with email@example.com (CCed) and me, if
> others want to join, we could start a "pkg-indicators" or something :)
Or it could be "pkg-ayatana" that takes care of packaging the software
that Ubuntu's Ayatana team releases:
I think this could be a good idea indeed. A team that would be very open
to the upstream Ubuntu/Canonical maintainers.
I saw that you used Git for the packaging, while I also use git for all
my own projects, I wonder if it would not make sense to use bzr for those
Canonical projects since they are all maintained in bzr, and it would make
it more likely to have upstream directly involved in the team.
What do you think?
Maybe James Westby could write an HOWTO for DD that are used to git on how
to best maintain Ubuntu's software within Debian with bzr-builddeb.
Like what I do? Sponsor me: http://ouaza.com/wp/2010/01/05/5-years-of-freexian/
My Debian goals: http://ouaza.com/wp/2010/01/09/debian-related-goals-for-2010/