all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: "Wiktor Żelazny" <wz@freeshell.de>
Cc: 57337@debbugs.gnu.org
Subject: [bug#57337] [PATCH 0/2] Add docxbox
Date: Thu, 08 Sep 2022 14:44:06 +0200	[thread overview]
Message-ID: <877d2ehw89.fsf@gnu.org> (raw)
In-Reply-To: <20220822092753.31295-1-wz@freeshell.de> ("Wiktor Żelazny"'s message of "Mon, 22 Aug 2022 11:27:53 +0200")

Hi,

Wiktor Żelazny <wz@freeshell.de> skribis:

> The docxbox patch is probably not ready for applying, yet (but it should
> be close). This is my first attempt at “unvendoring”. The thing builds
> and seems to work. The problem is that etc/ld.so.cache gets created. I
> have no idea where it comes from, but I suspect that it shouldn’t be
> there, as it’s easy to imagine a conflict if multiple packages with
> etc/ld.so.cache are being installed.

That’s OK: every package gets this file; see
<https://guix.gnu.org/en/blog/2021/taming-the-stat-storm-with-a-loader-cache/>
for background.

> Then, there are linter messages:
>
>    /home/<USER>/guix/guix-git/gnu/packages/textutils.scm:1512:12: docxbox@0.0.5: the source file name should contain the package name
>
> Adding the
>
>    (file-name (git-file-name name version))
>
> line removes the warning, but breaks the build.

Weird, how so?  The name shouldn’t have any impact on the build process.
Could you investigate a bit?

>    /home/<USER>/guix/guix-git/gnu/packages/textutils.scm:1512:12: docxbox@0.0.5: the source URI should not be an autogenerated tarball
>
> I’m guessing this refers to GitHub Automatic Releases feature.
> Unfortunately, there are no other releases to choose from in that
> repository.

In that case, use ‘git-fetch’ instead of referring to the generated
tarball.

> Finally, there’s the question related to the MS Word being proprietary
> software. I don’t think there should be controversies here, as docxbox
> is about interacting with the docx format, rather than the software
> itself. And the format itself is standardized. Perhaps the synopsis
> the package should avoid mentioning MS Word. I borrowed it from the
> docxbox repository.

It’s OK to mention Word to say that the tool allows you to read its
files.

Thanks,
Ludo’.




  parent reply	other threads:[~2022-09-08 13:17 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-22  9:27 [bug#57337] [PATCH 0/2] Add docxbox Wiktor Żelazny
2022-08-22  9:36 ` [bug#57337] [PATCH 1/2] gnu: Add miniz-cpp Wiktor Żelazny
2022-08-22  9:36   ` [bug#57337] [PATCH 2/2] gnu: Add docxbox Wiktor Żelazny
2022-09-08 12:49     ` [bug#57337] [PATCH 0/2] " Ludovic Courtès
2022-09-23 18:04       ` Wiktor Żelazny
2022-09-08 12:46   ` Ludovic Courtès
2022-09-23 17:46     ` Wiktor Żelazny
2022-09-08 12:44 ` Ludovic Courtès [this message]
2022-09-23 18:21   ` Wiktor Żelazny
2022-12-26 14:57 ` [bug#57337] [v2 " Wiktor Żelazny
2022-12-26 14:57   ` [bug#57337] [v2 1/2] gnu: Add miniz-cpp Wiktor Żelazny
2023-01-25 22:17     ` Ludovic Courtès
2022-12-26 14:57   ` [bug#57337] [v2 2/2] gnu: Add docxbox Wiktor Żelazny
2023-01-25 22:21     ` Ludovic Courtès
2023-01-28 19:50       ` Wiktor Żelazny
2023-02-05 20:18 ` [bug#57337] [PATCH v3 1/2] gnu: Add miniz-cpp Wiktor Żelazny
2023-02-05 20:18   ` [bug#57337] [PATCH v3 2/2] gnu: Add docxbox Wiktor Żelazny

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=877d2ehw89.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=57337@debbugs.gnu.org \
    --cc=wz@freeshell.de \
    /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.