unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Simon Tournier <zimon.toutoune@gmail.com>
To: Andy Tai <atai@atai.org>
Cc: 61010@debbugs.gnu.org
Subject: [bug#61010] [PATCH] gnu: Add icewm
Date: Wed, 25 Jan 2023 10:21:34 +0100	[thread overview]
Message-ID: <865ycv6kbl.fsf@gmail.com> (raw)
In-Reply-To: <CAJsg1E-TXfEw0Fx=LmVZghusMk3oKQoKNLfc1pTDE69dPhEr8g@mail.gmail.com>

Hi,

On Tue, 24 Jan 2023 at 23:37, Andy Tai <atai@atai.org> wrote:

> This I did not address in the revision because the second .tar.gz is
> available on the net, satisfying GPL's source requirement... but will
> revise if Guix policy demands otherwise

I do not understand what you mean.  My point is that these .gmo files
are generated by the author of the release and they are _not_ included in
the upstream source code – the Git repository.

For most of the cases, the Guix project tries hard to package only from
the source code, i.e., build as much as possible from scratch.

Hence, the question: do we re-generate these files?


Cheers,
simon

PS: Indeed, sorry for the typo in my previous message.  I wrote:

    Other said, these files are in the archive tar.gz [2].

when *not* is missing.  I wanted to say:

    Other said, these files are *NOT* in the archive tar.gz [2].




  parent reply	other threads:[~2023-01-25 10:11 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-22 20:37 [bug#61010] [PATCH] gnu: Add icewm Andy Tai
2023-01-23 17:33 ` [bug#61010] Andy Tai
2023-01-24 12:26 ` [bug#61010] [PATCH] gnu: Add icewm Simon Tournier
2023-01-25  7:37   ` Andy Tai
2023-01-25  7:50     ` Andy Tai
2023-01-25  9:21     ` Simon Tournier [this message]
2023-01-26  6:02       ` Andy Tai
2023-01-27 20:42         ` Andy Tai
2023-01-28  8:22 ` [bug#61010] [PATCH v3] " Andy Tai
2023-02-10  2:05   ` bug#61010: [PATCH] " 宋文武 via Guix-patches via
2023-02-06 11:43 ` [bug#61010] lost gtk input Feng Shu
2023-02-10  5:48   ` 宋文武 via Guix-patches via

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=865ycv6kbl.fsf@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=61010@debbugs.gnu.org \
    --cc=atai@atai.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).