all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: help-guix@gnu.org
Subject: Re: Need some help to remove non-free documentation
Date: Thu, 25 Oct 2018 09:28:14 +0200	[thread overview]
Message-ID: <87lg6mwkmp.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <87y3anzalx.fsf@gnu.org> ("Ludovic Courtès"'s message of "Wed, 24 Oct 2018 16:24:10 +0200")

Hello,

ludo@gnu.org (Ludovic Courtès) writes:

Thank you for your answer.

> What I would do in a ‘snippet’ or the origin is:
>
>   1. rm -rf doc
>
>   2. Remove “doc” from the ‘SUBDIRS’ variable of the top-level
>      Makefile.in.

That would remove all documentation. However, only a tiny part of it is
non-free. I'm trying to preserve some of it.

> That way you won’t need to regenerate the build files.
>
> Does that make sense or am I too naive?

IIUC, this will unfortunately not cut it.

> (Besides we should get in touch with the folks at Grenoble University to
> see if they would agree to liberating the docs.  Perhaps Debian people
> already attempted?)

Debian encounters the same problem, see
<https://salsa.debian.org/science-team/giac/blob/master/debian/giac-doc.README.Debian>.

I don't know if they attempted to contact the author, tho.

Regards,

-- 
Nicolas Goaziou

      reply	other threads:[~2018-10-25  7:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-22 12:32 Need some help to remove non-free documentation Nicolas Goaziou
2018-10-24 14:24 ` Ludovic Courtès
2018-10-25  7:28   ` Nicolas Goaziou [this message]

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

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

  git send-email \
    --in-reply-to=87lg6mwkmp.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --cc=help-guix@gnu.org \
    --cc=ludo@gnu.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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.