emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Simon Guest <sjg@cantab.net>
To: emacs-orgmode@gnu.org
Subject: Unbundling contrib from org-plus-contrib package?
Date: Fri, 11 Aug 2017 11:36:20 +1200	[thread overview]
Message-ID: <CAFhGSbtwiG0Atmc13JdupPqSbZ2FsY+Ykmg4Dnn6Vn-OwiKsRQ@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1320 bytes --]

Hiding in the ox-taskjuggler thread is a discussion of some of the problems
caused by having contrib bundled up in the org-plus-contrib package.  (See
that thread for the details.)

However, a general question remains, as asked by Tim Cross, whom I will
quote if I may:

There are also some other alternatives on the emacs-devel list from when
> I asked as a general question regarding package.el and dependencies.
> Should be noted that this issue is primarily caused because, fro the
> package.el perspective, org-plus-contrib is different to the org
> package. Other ELPA/MELPA/etc packages have org as a dependency and not
> org-plus-contrib. There is no support in package.el for alternative
> dependencies.
> I would be interested in understanding the rationale for having
> org-plus-contrib rather than just an org package and an org-contrib
> package? It should be possible to just have an org-contrib package which
> depends on an org package (of same version). This would then avoid this
> issue. As this is an obvious solution, I suspect there is something
> subtle which unpins the rationale to have an org and org-plus-contrib
> package approach, but don't know what that is.


So, is there an answer to this good and as-yet unanswered question about
unbundling contrib into its own package?

cheers,
Simon

[-- Attachment #2: Type: text/html, Size: 2459 bytes --]

                 reply	other threads:[~2017-08-10 23:36 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=CAFhGSbtwiG0Atmc13JdupPqSbZ2FsY+Ykmg4Dnn6Vn-OwiKsRQ@mail.gmail.com \
    --to=sjg@cantab.net \
    --cc=emacs-orgmode@gnu.org \
    /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).