emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Joost Kremers <joostkremers@fastmail.fm>
To: Ihor Radchenko <yantar92@gmail.com>
Cc: "András Simonyi" <andras.simonyi@gmail.com>,
	"Bruce D'Arcus" <bdarcus@gmail.com>,
	alain.cochard@unistra.fr, emacs-orgmode@gnu.org
Subject: Re: Can citeproc be installed without using MELPA? (was: @string abbreviation in bib file not honored in (basic) org-cite)
Date: Sun, 10 Jul 2022 21:37:46 +0200	[thread overview]
Message-ID: <87mtdgg3cc.fsf@fastmail.fm> (raw)
In-Reply-To: <87fsj9uxtu.fsf@localhost>

On Sun, Jul 10 2022, Ihor Radchenko wrote:
> András Simonyi <andras.simonyi@gmail.com> writes:
>>> The problem with parsebib is that it does not even have license
>>> (I do not see any in https://github.com/joostkremers/parsebib). If
>>> parsebib were a part of Emacs core or at least a part of ELPA, we would
>>> also be able to use it in Org core.
>> looking into the source code (parsebib.el), the library seems to be
>> under a BSD-type license.

Yes, it is. It's a single file and the license is at the top. I can add a
separate license file if that's necessary.

> Then, I am wondering if parsebib can be added to ELPA or at least
> non-GNU ELPA. The same can be said for all other dependencies of
> citeproc.el and for citeproc itself.

I'd have no problem if it were added to non-GNU ELPA. GNU ELPA is a little
difficult because I don't have a copyright assignment on file. (It's proven a
little difficult to get someone in the company to sign the corporate waiver...)

Joost Kremers
Life has its moments

  reply	other threads:[~2022-07-10 19:45 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-08 11:17 @string abbreviation in bib file not honored in (basic) org-cite Alain.Cochard
2022-07-08 12:05 ` Bruce D'Arcus
2022-07-09  3:55   ` Ihor Radchenko
2022-07-09  8:40     ` András Simonyi
2022-07-10  9:22       ` Can citeproc be installed without using MELPA? (was: @string abbreviation in bib file not honored in (basic) org-cite) Ihor Radchenko
2022-07-10 19:37         ` Joost Kremers [this message]
2022-07-11  2:06           ` Ihor Radchenko
2022-07-12 10:23             ` András Simonyi
2022-07-09  6:10   ` @string abbreviation in bib file not honored in (basic) org-cite [and a minimal working example with natbib] Alain.Cochard
2022-07-09 12:40     ` Bruce D'Arcus
2022-07-10  7:17     ` Ihor Radchenko
2022-07-12 11:14       ` András Simonyi
2022-07-12 11:36         ` John Kitchin
2022-07-12 11:48           ` András Simonyi
2022-07-13  4:52     ` Alain.Cochard
2022-08-07 14:08       ` Ihor Radchenko
2022-07-17  8:26 ` @string abbreviation in bib file not honored in (basic) org-cite Ihor Radchenko
2022-07-17  8:52   ` Alain.Cochard
2022-07-19 20:35   ` Joost Kremers
2022-07-19 20:40     ` Bruce D'Arcus
2022-07-20 10:46       ` Joost Kremers
2022-07-28 12:12         ` Ihor Radchenko
2022-07-29  8:02           ` Joost
2022-10-30  6:25             ` Ihor Radchenko
2022-11-02 21:54               ` Joost Kremers
2022-11-03  7:25                 ` Ihor Radchenko
2022-11-04 14:26                   ` Joost Kremers
2022-11-05  8:13                     ` Ihor Radchenko
2022-11-07 18:41                       ` Joost Kremers

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:

  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=87mtdgg3cc.fsf@fastmail.fm \
    --to=joostkremers@fastmail.fm \
    --cc=alain.cochard@unistra.fr \
    --cc=andras.simonyi@gmail.com \
    --cc=bdarcus@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=yantar92@gmail.com \


* 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


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).