unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: "Sergio Pastor Pérez" <sergio.pastorperez@outlook.es>
To: jgart <jgart@dismail.de>, 67755@debbugs.gnu.org
Subject: [bug#67755] [PATCH] gnu: Add imhex.
Date: Mon, 01 Jul 2024 19:02:25 +0200	[thread overview]
Message-ID: <PAXP251MB0348CDC3D06F4EC738251BF0F3D32@PAXP251MB0348.EURP251.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <87r0ceqign.fsf@dismail.de>

Hi! Thanks for taking a look.

jgart <jgart@dismail.de> writes:

> Are you planning on resolving those TODO items soonish?

This is what I was explaining on the version 2 of the patch. It's not
something that should be fixed at the package level. I've discussed it
with the maintainers, until they don't implement a proper way of
externalizing the handling of libraries we should be using the
submodules.

Having said that, I think the package is ready, is there any reason why
you don't find it adequate, aside from the bundled libraries? We can
remove the comments if that's what worries you.

As a side note, I tried to un-bundle the libraries and the amount of
patching that it requires is unreasonable, every library requires it's
own CMAKE find file, which is responsibility of the software
developers. This is why I say that this should be done upstream.

I suggest to merge it as it is and I will update the package definition
once ImHex properly supports using system libraries. I don't think the
maintainers have this on their priority list so I don't know how long it
could take.

I will send a v3 of this patch without the comments and without the
redundant flags.

> If you'd like to make this package easily available to others before its
> ready for upstream I would recommend creating a channel for it.

I have it already available on my channel.

Thanks for your time!
Have a good evening,
Sergio.




  reply	other threads:[~2024-07-01 17:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-10 20:06 [bug#67755] [PATCH] gnu: Add imhex Sergio Pastor Pérez
2024-06-29 12:15 ` [bug#67755] [PATCH v2] " Sergio Pastor Pérez
2024-06-30 20:33   ` [bug#67755] [PATCH] " jgart via Guix-patches via
2024-07-01 17:02     ` Sergio Pastor Pérez [this message]
2024-07-01 16:55 ` [bug#67755] [PATCH v3] " Sergio Pastor Pérez

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=PAXP251MB0348CDC3D06F4EC738251BF0F3D32@PAXP251MB0348.EURP251.PROD.OUTLOOK.COM \
    --to=sergio.pastorperez@outlook.es \
    --cc=67755@debbugs.gnu.org \
    --cc=jgart@dismail.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 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).