> Finally, I don't think it would serve current and potential users of
> Ion on Debian to rename it. We just about get away with Iceweasel as
> that controversy was widely publicised and the package is part of a
> standard desktop installation. For any more obscure application I
> fear renaming
On Tue, 22 May 2007, Ben Hutchings wrote:
> Firstly, I do not want to maintain a renaming patch. There are many
> separate instances of "Ion" and "Ion3" in documentation, messages,
> etc. I believe this would be a continuing maintenance chore.
Well, some of those references have to stay, because t
On Sun, 2007-05-20 at 23:46 -0400, Benj. Mako Hill wrote:
>
> > On Thu, 17 May 2007, Ben Hutchings wrote:
> > > After discussing with upstream, I'm complying with the trademark licence
> > > conditions by "prominent version qualifiers and notices of possible
> > > out-datedness" rather than renami
> On Thu, 17 May 2007, Ben Hutchings wrote:
> > After discussing with upstream, I'm complying with the trademark licence
> > conditions by "prominent version qualifiers and notices of possible
> > out-datedness" rather than renaming. Specifically, for a fresh
> > installation, the postinst checks
On Thu, 17 May 2007, Ben Hutchings wrote:
> After discussing with upstream, I'm complying with the trademark licence
> conditions by "prominent version qualifiers and notices of possible
> out-datedness" rather than renaming. Specifically, for a fresh
> installation, the postinst checks the upstre
After discussing with upstream, I'm complying with the trademark licence
conditions by "prominent version qualifiers and notices of possible
out-datedness" rather than renaming. Specifically, for a fresh
installation, the postinst checks the upstream version (using uscan) and
if the version being
On Wed, May 09, 2007 at 12:41:34AM +0100, Ben Hutchings wrote:
> On Mon, 2007-05-07 at 07:28 -0400, Mike O'Connor wrote:
> > Unfortunately, the release you are pointing to comes with a license change
> > that affects debian. The following was added as a preamble tothe LGPL:
>
> > This license cha
Unfortunately, the release you are pointing to comes with a license change
that affects debian. The following was added as a preamble tothe LGPL:
The code of this project is "essentially" licensed under the LGPL, version
2.1, unless otherwise indicated in components taken from elsewhere. It is
re
8 matches
Mail list logo
