From: "Dr. Arne Babenhauserheide" <firstname.lastname@example.org> To: Arthur Miller <email@example.com> Cc: Christopher Dimech <firstname.lastname@example.org>, email@example.com Subject: Re: The fate of ditaa.jar (9.4.5.) Date: Wed, 12 May 2021 11:41:48 +0200 [thread overview] Message-ID: <firstname.lastname@example.org> (raw) In-Reply-To: <AM9PR09MB4977D3FD673827BD932BA48D96529@AM9PR09MB4977.eurprd09.prod.outlook.com> [-- Attachment #1: Type: text/plain, Size: 1588 bytes --] Arthur Miller <email@example.com> writes: > I don't think that would be the case. Java is considered unsafe software > so I wouldn't rely on older versions being pre-installed and avialable everywhere. Java is not considered unsafe software — not any more than any interpreted language. What’s unsafe are Java applets, but those are not what ditaa uses. >> I would bundle the old version to keep old documents working (I do not >> want org-mode to be volatile software that breaks existing documents >> with an update), but notify the user that a new version exists. > > Since you already have Java and ditaa installed on your computer, your > older documents won't get broken. I have Java, but not ditaa, because Java is packaged in my distribution and ditaa is not. My build pipelines use ditaa as shipped with org-mode. Different from plantuml, there is no ditaa-runner to install as application. So unbundling ditaa breaks my documents when updating org-mode. The same for everyone else who used a standard ditaa-setup with org-mode. > By the way, how difficult is to download one file from the internet > (ditaa.jar) if you are an user? That’s not the point. The point is that every single user with a ditaa block has to do it. Ask the other way round: What is the benefit of removing ditaa from org? If you want to force most current org-ditaa users to unbreak their setup after update, there should be a significant tangible benefit. Best wishes, Arne -- Unpolitisch sein heißt politisch sein ohne es zu merken [-- Attachment #2: signature.asc --] [-- Type: application/pgp-signature, Size: 1125 bytes --]
next prev parent reply other threads:[~2021-05-12 9:43 UTC|newest] Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-05-10 11:28 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 [this message] 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 ` he " Christopher Dimech 2021-05-11 8:36 ` The " 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 \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: The fate of ditaa.jar (9.4.5.)' \ /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
Code repositories for project(s) associated with this 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).