unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Marius Bakke <marius@gnu.org>
To: david larsson <david.larsson@selfhosted.xyz>, 47898@debbugs.gnu.org
Subject: [bug#47898] [PATCH] [core-updates] Add option --xpath0 to xmllint from libxml2
Date: Thu, 13 May 2021 14:41:46 +0200	[thread overview]
Message-ID: <87eeeaiz5h.fsf@gnu.org> (raw)
In-Reply-To: <20aec8da67d18b52e5a166f45cab40b2@selfhosted.xyz>

[-- Attachment #1: Type: text/plain, Size: 958 bytes --]

david larsson <david.larsson@selfhosted.xyz> skriver:

> Hi!
> This patch adds the option to separate xpath results from xmllint by a 
> null delimiter when using the --xpath0 option-flag. It is something 
> that's been asked for for a long time by users on stackoverflow and 
> merge-attempts have been made to upstream without success.
>
> Examples:
>    - https://gitlab.gnome.org/GNOME/libxml2/-/issues/227
>    - https://gitlab.gnome.org/GNOME/libxml2/-/merge_requests/8

I'm reluctant to take a patch that has been rejected upstream,
especially for a core package such as libxml2.  Porting can be
time-consuming which delays security updates, and we'll have situations
where something "works on Guix" but not elsewhere (or vice versa).

Will adding it as a separate package be sufficient?  We could call it
"xmllint-xpath0" or similar and make it clear that it's just libxml2
with a patched xmllint in the description.

Thoughts?

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]

  reply	other threads:[~2021-05-13 12:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-19 18:48 [bug#47898] [PATCH] [core-updates] Add option --xpath0 to xmllint from libxml2 david larsson
2021-05-13 12:41 ` Marius Bakke [this message]
2021-05-13 13:21   ` david larsson
2021-05-13 13:29     ` Marius Bakke
     [not found]       ` <80bc8f6c73d5aa423cf906d59bbcd43e@selfhosted.xyz>
2021-05-15 12:53         ` david larsson
2021-05-15 16:12           ` Marius Bakke
2021-05-15 17:12             ` david larsson
2021-05-15 19:21             ` david larsson
2021-05-18 20:25               ` bug#47898: " Marius Bakke

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=87eeeaiz5h.fsf@gnu.org \
    --to=marius@gnu.org \
    --cc=47898@debbugs.gnu.org \
    --cc=david.larsson@selfhosted.xyz \
    /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).