emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Christopher Dimech <dimech@gmx.com>
To: "Dr. Arne Babenhauserheide" <arne_bab@web.de>
Cc: Tim Cross <theophilusx@gmail.com>, emacs-orgmode@gnu.org
Subject: he fate of ditaa.jar (9.4.5.)
Date: Tue, 11 May 2021 08:53:29 +0200	[thread overview]
Message-ID: <trinity-e13db107-4636-4756-8cdf-785f7dc1485d-1620716009779@3c-app-mailcom-bs03> (raw)
In-Reply-To: <875yzpkcal.fsf@web.de>

> Sent: Tuesday, May 11, 2021 at 6:35 PM
> From: "Dr. Arne Babenhauserheide" <arne_bab@web.de>
> To: "Tim Cross" <theophilusx@gmail.com>
> Cc: emacs-orgmode@gnu.org
> Subject: Re: The fate of ditaa.jar (9.4.5.)
>
> 
> Tim Cross <theophilusx@gmail.com> writes:
> > I agree. As pointed out already, just bundling the jar file is not
> > sufficient as you need a java runtime as well.
> 
> Java is available in my distribution, ditaa is not. Removing ditaa from
> org means that I have to do manual installation and configuration, while
> with ditaa bundled, org-mode can simply note that I need java installed.
> 
> > If we bundle it, we also need to ensure it is updated if/when new jar
> > versions are released.
> 
> We can do that, but we don’t have to. As long as the bundled jar works,
> it is much better than no jar. And users can use newer version as they
> like by changing the jar-path.

A jar that works would be good as initial setup, then people can change that
as they wish.

> Note that this isn’t about security, since even if an old version of
> ditaa should turn out to be vulnerable, this would still be less
> dangerous than a shell-block. Therefore old versions of ditaa are
> completely fine.
> 
> Best wishes,
> Arne
> -- 
> Unpolitisch sein
> heißt politisch sein
> ohne es zu merken
>


  reply	other threads:[~2021-05-11  7:01 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-10 11:28 The fate of ditaa.jar (9.4.5.) Jarmo Hurri
2021-05-10 11:50 ` Eric S Fraga
2021-05-10 12:28 ` Russell Adams
2021-05-10 17:07   ` Dr. Arne Babenhauserheide
2021-05-10 20:49     ` Arthur Miller
2021-05-11  1:22       ` Christopher Dimech
2021-05-11 18:56         ` Arthur Miller
2021-05-11 20:53           ` Dr. Arne Babenhauserheide
2021-05-12  8:44             ` Arthur Miller
2021-05-12  9:41               ` Dr. Arne Babenhauserheide
2021-05-12 14:51                 ` Russell Adams
2021-05-13 12:44                 ` Jarmo Hurri
2021-05-13 14:06                   ` Arthur Miller
2021-05-13 20:08                     ` Dr. Arne Babenhauserheide
2021-05-14  1:13                       ` Arthur Miller
2021-05-14  5:30                         ` Dr. Arne Babenhauserheide
2021-05-14  5:39                           ` Christopher Dimech
2021-05-14 11:23                             ` Arthur Miller
2021-05-14 11:57                               ` Christopher Dimech
2021-05-10 18:41 ` Nick Dokos
2021-05-11  1:25   ` Christopher Dimech
2021-05-11  4:33   ` Tim Cross
2021-05-11  6:35     ` Dr. Arne Babenhauserheide
2021-05-11  6:53       ` Christopher Dimech [this message]
2021-05-11  8:36       ` Tim Cross
2021-05-11 12:52         ` TEC
2021-05-11 19:15           ` Arthur Miller
2021-05-12  0:06           ` Tim Cross
2021-05-12  8:47             ` Arthur Miller
2021-05-15 17:31           ` [External] : " Daniel Ortmann
2021-05-11 19:02       ` Arthur Miller
2021-05-16 12:19 ` Bastien

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://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=trinity-e13db107-4636-4756-8cdf-785f7dc1485d-1620716009779@3c-app-mailcom-bs03 \
    --to=dimech@gmx.com \
    --cc=arne_bab@web.de \
    --cc=emacs-orgmode@gnu.org \
    --cc=theophilusx@gmail.com \
    /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/emacs/org-mode.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).