From: ludo@gnu.org (Ludovic Courtès)
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: help-guix@gnu.org
Subject: Re: Need some help to remove non-free documentation
Date: Wed, 24 Oct 2018 16:24:10 +0200 [thread overview]
Message-ID: <87y3anzalx.fsf@gnu.org> (raw)
In-Reply-To: <87mur6yxe3.fsf@nicolasgoaziou.fr> (Nicolas Goaziou's message of "Mon, 22 Oct 2018 14:32:52 +0200")
Hello Nicolas,
Nicolas Goaziou <mail@nicolasgoaziou.fr> skribis:
> I'm trying to remove non-free documentation from "giac-xcas" package.
>
> It involves removing some files from "doc/" subdirectory in source and
> updating "Makefile.am". As a consequence, "Makefile.in" has to be
> updated accordingly. Pain ensues.
:-)
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 way you won’t need to regenerate the build files.
Does that make sense or am I too naive?
(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?)
HTH!
Ludo’.
next prev parent reply other threads:[~2018-10-24 14:24 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 [this message]
2018-10-25 7:28 ` Nicolas Goaziou
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=87y3anzalx.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=help-guix@gnu.org \
--cc=mail@nicolasgoaziou.fr \
/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.
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).