[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#402650: ITP: mozilla-foxyproxy -- advanced proxy management tool for iceweasel

On Tue, Dec 12, 2006 at 08:13:41PM +0100, Mike Hommey wrote:
> On Tue, Dec 12, 2006 at 07:55:59PM +0100, Alexander Sack <asac@debian.org> wrote:
> > On Tue, Dec 12, 2006 at 07:41:30PM +0100, Mike Hommey wrote:
> > > On Tue, Dec 12, 2006 at 11:19:22AM +0100, Alexander Sack <asac@debian.org> wrote:
> > > > I don't think we should still use the mozilla-* prefix for extension
> > > > packages ... now that we have ice*.
> > > 
> > > But then, what to use instead ?
> > 
> > Reading from the package description, this extension is just for
> > iceweasel ... so maybe iceweasel-foxyproxy ... 
> With a little work, such an extension could be made available for
> iceape. That may even happen upstream. So iceweasel-something is out of
> the question, IMHO.
> > or just foxyproxy
> > with the term "iceweasel extension" in the package short description.
> or debtags ?

Yes, using debtags for extensions together with a good short
description is definitly a good idea.

> Anyways, the thing is that when I uploaded the very first extension
> packages, for mozilla at the time, they didn't have the mozilla in their
> name. Now they have, because of fair comments from Ari Pollak in bug
> #189595. And I still agree with him.

One reason ari gave was that the package name might give the user the
false impression that the package ships a standalone program. However
later we introduced mozilla-firebird et al ... which obviously were
standalone programs ... rather confusing.

That said ... I think that the package name is the wrong place to
encode arbitrary information that one considers important to
communicate to users (even more if its encoded in a implicit manner,
e.g. 'mozilla-' vs. '-extension'). Users will never be able to guess
what they can expect from installing an arbitrary package by just
looking at its name ... we have other means to communicate that kind
of info.

So, for me the most consistent practice for packaging ice* extensions
post etch would be to use the extension name as package name and put
info about its relation to our ice-apps into (short) description and

 - Alexander

 GPG messages preferred.    |  .''`.  ** Debian GNU/Linux **
 Alexander Sack             | : :' :      The  universal
 asac@debian.org            | `. `'      Operating System
 http://www.asoftsite.org/  |   `-    http://www.debian.org/

Reply to: