From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Empty doc-dir for nettle - needful thing?
Date: Sun, 05 Mar 2017 11:32:29 +0000 [thread overview]
Message-ID: <1488713549.2451.0.camel@ipfire.org> (raw)
In-Reply-To: <c0c10659-9d9b-6f63-f684-93e7e2cb436c@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 714 bytes --]
Hello,
yes, it is a good idea to drop this. We don't ship any development
documentation on the systems anyway so if there is a switch, feel free
to activate that.
Best,
-Michael
On Sun, 2017-03-05 at 09:48 +0100, Matthias Fischer wrote:
> Hi,
>
> This just came to my view:
>
> Do we really need the (empty) '/usr/share/doc'-directory for nettle?
>
> Its installed through lfs:
>
> ...
> install -v -m755 -d /usr/share/doc/nettle-3.3
> ...
>
> And its ~active in nettle-rootfile which leads to an empty directory:
> '/usr/share/doc/nettle[VERSION].
>
> Is this needed/intentional?
>
> Or could it be built with '--disable-documentation' and perhaps save
> some time and ~space? ;-)
>
> Best,
> Matthias
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2017-03-05 11:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-05 8:48 Matthias Fischer
2017-03-05 11:32 ` Michael Tremer [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=1488713549.2451.0.camel@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=development@lists.ipfire.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox