unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: racin@free.fr
Cc: 60820 <60820-done@debbugs.gnu.org>
Subject: bug#60820: [PATCH] Add 'totpages' latex package.
Date: Tue, 18 Apr 2023 15:33:50 +0200	[thread overview]
Message-ID: <87ttxdjow1.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <878rhol59o.fsf@nicolasgoaziou.fr> (Nicolas Goaziou's message of "Fri, 27 Jan 2023 10:02:11 +0100")

Hello,

Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:

> racin@free.fr writes:
>
>> But if someone need the source, my understanding is that one can just use guix  build -S 
>> or some other command to retrieve them.
>> So I don't see the interest of having them too in the compiled output, as they are not useful for 
>> normal usage of the package; it seems to take up space for no reason.
>
> I don't know if the reason is strong enough, but I gave you one above.
>
> In any case, the main nit here is that we try to generate files from
> source, which "#trivial? #t" prevents.

I renamed the package, updated its definition, set propagated inputs,
and applied it. Thank you for the initial work.

You make a fair point with the source distribution, but unfortunately,
it didn't raise much interest so far. It might be worth asking it on
Guix Devel ML.

Meanwhile, I'm closing this bug.

Regards,
-- 
Nicolas Goaziou




      reply	other threads:[~2023-04-18 13:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-14 22:36 [bug#60820] [PATCH] Add 'totpages' latex package Matthieu Lemerre
2023-01-15 18:26 ` Nicolas Goaziou
2023-01-23 21:55   ` racin
2023-01-24 13:16     ` Nicolas Goaziou
2023-01-24 22:25       ` racin
2023-01-25 16:35         ` Nicolas Goaziou
2023-01-25 17:42           ` racin
2023-01-27  9:02             ` Nicolas Goaziou
2023-04-18 13:33               ` 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

  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=87ttxdjow1.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --cc=60820-done@debbugs.gnu.org \
    --cc=racin@free.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.
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).