unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Nils Gillmann <ng0@n0.is>
To: Mark H Weaver <mhw@netris.org>
Cc: guix-devel <guix-devel@gnu.org>, Nils Gillmann <ng0@n0.is>
Subject: Re: Looking for Thunderbird/Icedove
Date: Tue, 3 Apr 2018 19:23:52 +0000	[thread overview]
Message-ID: <20180403192352.5zpe5oubs23q3jvd@abyayala> (raw)
In-Reply-To: <87tvsscdqe.fsf@netris.org>

Mark H Weaver transcribed 1.3K bytes:
> Hi Nils,
> 
> Nils Gillmann <ng0@n0.is> writes:
> 
> > Björn Höfling transcribed 1.2K bytes:
> >
> >> Are there any more recent news on the Thunderbird side? Does anyone have
> >> more-or-less ready snippets available?
> >
> > I can not post the link to straight-out of the box Thunderbird here
> > (current repository is against the policy in Guix), but if you really
> > want to work on it I can send you the link offlist (just contact me at
> > gillmann@infotropique.org).
> 
> Did someone tell you that you shouldn't post a preliminary
> Thunderbird/Icedove package definition to this mailing list?

No. It just exists in a branch in an (experimental, fluid) repository where
other nonfree software (partially as a base for other builds to be upstreamed)
is located in, which is why I mentioned "policy reasons". If that's an exception
I could link to the cgit, I'll do it of course.

If the repo is not okay, I can send a mbox formated patch.

> If so, can you show me the email?
> 
> It's true that we shouldn't post package definitions for nonfree
> software on the Guix mailing lists.  However, Thunderbird/Icedove has
> only a couple of known freedom issues which have apparently already been
> addressed in Parabola GNU/Linux:
> 
>   https://libreplanet.org/wiki/List_of_software_that_does_not_respect_the_Free_System_Distribution_Guidelines#Thunderbird
> 
> Given that a GNU FSDG compliant version of Thunderbird/Icedove already
> exists, and that we could surely apply the same fixes to our package, I
> see no problem with you posting your preliminary package definition.
> Please do so.  It would enable other interested developers to continue
> your work.
> 
>     Regards,
>       Mark

  reply	other threads:[~2018-04-03 19:23 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-03 13:49 Looking for Thunderbird/Icedove Björn Höfling
2018-04-03 16:48 ` Nils Gillmann
2018-04-03 19:05   ` Mark H Weaver
2018-04-03 19:23     ` Nils Gillmann [this message]
2018-04-03 19:45       ` Mark H Weaver
2018-04-03 20:02         ` Nils Gillmann
2018-04-03 21:37           ` Björn Höfling
2018-04-04  8:34             ` Ludovic Courtès
2018-04-04  9:09               ` Nils Gillmann
2018-04-04  5:14 ` Mark H Weaver
2018-04-05  5:21   ` Björn Höfling
2018-04-06 14:07   ` Mark H Weaver
  -- strict thread matches above, loose matches on Subject: below --
2018-04-03 16:33 Rene
2018-04-03 16:43 ` Nils Gillmann

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180403192352.5zpe5oubs23q3jvd@abyayala \
    --to=ng0@n0.is \
    --cc=guix-devel@gnu.org \
    --cc=mhw@netris.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).