emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Tim Cross <theophilusx@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: The fate of ditaa.jar (9.4.5.)
Date: Tue, 11 May 2021 14:33:20 +1000	[thread overview]
Message-ID: <8735utdgs4.fsf@gmail.com> (raw)
In-Reply-To: <87h7jaqvne.fsf@alphaville.usersys.redhat.com>


Nick Dokos <ndokos@gmail.com> writes:

> Jarmo Hurri <jarmo.hurri@iki.fi> writes:
>
>> Greetings.
>>
>> I pulled the latest master and noticed that contrib has been moved into
>> a separate repository. I also cloned this contrib repository, but can
>> not find the file
>>
>> scripts/ditaa.jar
>>
>> in the repo. In fact, there is no directory scripts in the repo.
>>
>> The documentation in the latest master states that
>>
>> Stathis Sideris wrote the ‘ditaa.jar’ ASCII to PNG converter that is now
>> packaged into the org-contrib repository.
>>
>> How should I proceed? Should I build this separately
>>
>> https://github.com/stathissideris/ditaa
>
> You don't need to build it: it's available in the release area
>
> https://github.com/stathissideris/ditaa/releases
>
>>
>> or will it still be included into contrib?
>
> In general, I think it's a better idea to point to the canonical sources
> and document how to integrate it into Org mode, than bundle things like
> that, but I have no idea how things are going to go. I'm sure there will
> be some problems that will need fixing one way or another.

I agree. As pointed out already, just bundling the jar file is not
sufficient as you need a java runtime as well. If we bundle it, we also
need to ensure it is updated if/when new jar versions are released. 

Better to clearly document where to get the dependencies and point to
the appropriate installation instructions.

I think we also need to keep in mind that we are currently in a bit of a
transition stage with the move to using ELPA and non-gnu ELPA. There
will be teething problems needing to be worked through both before and
after the transition. 
-- 
Tim Cross


  parent reply	other threads:[~2021-05-11  4:41 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
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 [this message]
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 \
    --in-reply-to=8735utdgs4.fsf@gmail.com \
    --to=theophilusx@gmail.com \
    --cc=emacs-orgmode@gnu.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).