From: Timotej Lazar <timotej.lazar@araneo.si>
To: Leo Prikler <leo.prikler@student.tugraz.at>, 49235@debbugs.gnu.org
Subject: [bug#49235] [PATCH] gnu: Add oneko.
Date: Sun, 27 Jun 2021 21:45:27 +0200 [thread overview]
Message-ID: <871r8nnlbc.fsf@araneo.si> (raw)
In-Reply-To: <beb6c3c61192797ee6eb1d959e4b9a5f88529da9.camel@student.tugraz.at>
Leo Prikler <leo.prikler@student.tugraz.at> [2021-06-27 21:24:00+0200]:
> I think the Debian patch says it best in that there might be copyright
> issues.
OK, I’ll copy / adjust that one then. :)
> To be fair, I only looked at the snippet, not what it produced, so it
> might actually be that it already did the correct thing. Are there
> directory, which are matched by .*\\.xbm?
The snippet only deletes the *xbm files. There is also (for instance)
bsd.include that #includes the relevant bitmaps and is in turn #included
by the main source file. The latter #include statements are removed by
the patch.
I didn’t delete bsd.include (and others) in the snippet since they don’t
have copyright issues and it would make the snippet a bit messier. A
COPYRIGHT file for the BSD daemon also remains. If that is problematic,
I can adjust the snippet to also delete these files. In any case, none
of them gets copied to the output.
next prev parent reply other threads:[~2021-06-27 19:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-26 19:20 [bug#49235] [PATCH] gnu: Add oneko Timotej Lazar
2021-06-27 12:45 ` Leo Prikler
2021-06-27 13:40 ` Timotej Lazar
2021-06-27 13:55 ` Leo Prikler
2021-06-27 17:51 ` Timotej Lazar
2021-06-27 18:24 ` Leo Prikler
2021-06-27 19:06 ` Timotej Lazar
2021-06-27 19:24 ` Leo Prikler
2021-06-27 19:45 ` Timotej Lazar [this message]
2021-06-27 19:50 ` Leo Prikler
2021-06-27 17:49 ` [bug#49235] [PATCH v2] " Timotej Lazar
2021-06-28 17:02 ` [bug#49235] [PATCH v3] " Timotej Lazar
2021-06-28 19:05 ` bug#49235: " Leo Prikler
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=871r8nnlbc.fsf@araneo.si \
--to=timotej.lazar@araneo.si \
--cc=49235@debbugs.gnu.org \
--cc=leo.prikler@student.tugraz.at \
/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.