From: "宋文武 via Guix-patches via" <guix-patches@gnu.org>
To: Frank Pursel <frank.pursel@gmail.com>
Cc: 53908@debbugs.gnu.org
Subject: [bug#53908] [PATCH] Adding a package for ditaa
Date: Fri, 05 Aug 2022 10:00:49 +0800 [thread overview]
Message-ID: <8735eb78ku.fsf_-_@envs.net> (raw)
In-Reply-To: <87leyhjesw.fsf@gmail.com> (Frank Pursel's message of "Fri, 11 Feb 2022 13:04:15 -0800")
Hello, a friendly ping here.
Frank Pursel <frank.pursel@gmail.com> writes:
> Hi,
>
> My intentions were good but this isn't good. I now see that though this
> ditaa package will build and work this package isn't yet ready for guix.
> If you want to help advance this, read on! I'll point out what I
> perceive I missed on the first go around. I still eventually hope to
> get ditaa officially packaged for guix.
>
> I belatedly see that I've stumbled into some less than desirable
> practices here. So, to be quick, ditaa in guix needs to wait until the
> underlying dependencies in java-batik-all-jar are under approriate build
> control.
>
> I now see that the current java-batik-all-jar build depends on the use
> of several jars embedded in the apache source package. It isn't guixy
> to use these. We need to provide guix built packages to replace those
> jars (some of which already exists).
I find that the batik source package of debian didn't have jars:
http://deb.debian.org/debian/pool/main/b/batik/batik_1.14-2.debian.tar.xz
So maybe it's actually not needed, and we can safely remove them in a
source snippet?
next prev parent reply other threads:[~2022-08-05 2:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-09 21:48 [bug#53908] [PATCH] Adding a package for ditaa Frank Pursel
2022-02-10 16:02 ` [bug#53908] [PATCH] Cleanups for the ditaa pkg Frank Pursel
2022-02-11 21:04 ` [bug#53908] [PATCH] Opportunities Frank Pursel
2022-08-05 2:00 ` 宋文武 via Guix-patches via [this message]
2023-01-20 23:37 ` bug#53908: [PATCH] Adding a package for ditaa Frank Pursel
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=8735eb78ku.fsf_-_@envs.net \
--to=guix-patches@gnu.org \
--cc=53908@debbugs.gnu.org \
--cc=frank.pursel@gmail.com \
--cc=iyzsong@envs.net \
/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).