unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: "Collin J. Doering" <collin@rekahsoft.ca>
To: zimoun <zimon.toutoune@gmail.com>
Cc: 50374@debbugs.gnu.org
Subject: [bug#50374] [PATCH 0/1] Add org-roam-extensions package
Date: Thu, 16 Sep 2021 09:48:25 -0400	[thread overview]
Message-ID: <87wnngfwv9.fsf@rekahsoft.ca> (raw)
In-Reply-To: <86fsu7tk4v.fsf@gmail.com>

Hi Zimoun,

Thanks for taking the time to look at this patch.

On 14 Sep 2021 at 14:30, zimoun <zimon.toutoune@gmail.com> wrote:

> Hi,
>
> On Sat, 04 Sep 2021 at 12:12, "Collin J. Doering" <collin@rekahsoft.ca> wrote:
>> Instead of the implementation put forth in
>> https://issues.guix.gnu.org/50333 this change includes org-roam
>> extensions as a separate package.
>
> Naive question, why should the extensions be distributed as a separate
> package?

They are not required for the use of org-roam. They could also be
distributed as an additional output on the org-roam package itself.
Happy to re-adjust if that's preferred.

> Well, I am not an Org-Roam user… having the extensions along with the
> package emacs-org-roam seem the best; other said, why an Org-Roam user
> would be annoyed to have these extensions and not use them?

I don't think they need to be included directly in the main output of
the emacs-org-roam package as not all org-roam users will leverage them.
However I can't think of any reasons why a org-roam user would be
annoyed that they are included (other then including software that is
not used, which is not necessarily favorable).

Please let me know your preference between the following:

1. org-roam extensions as part of a separate package (this is what is
already presented in this patch set). 
2. Extensions as a separate `extensions` output on the emacs-org-roam package
3. Build the extensions directly into the primary output of the
emacs-org-roam package (this is already done in https://issues.guix.gnu.org/50333)

> All the best,

You too!

-- 
Collin J. Doering

http://rekahsoft.ca
http://blog.rekahsoft.ca
http://git.rekahsoft.ca




  reply	other threads:[~2021-09-16 13:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-04 16:12 [bug#50374] [PATCH 0/1] Add org-roam-extensions package Collin J. Doering
2021-09-04 16:19 ` [bug#50374] [PATCH 1/1] gnu: Add emacs-org-roam-extensions Collin J. Doering
2021-09-12 16:19 ` [bug#50374] (no subject) Adolfo De Unánue
2021-09-16 13:38   ` Collin J. Doering
2021-09-14 12:30 ` [bug#50374] [PATCH 0/1] Add org-roam-extensions package zimoun
2021-09-16 13:48   ` Collin J. Doering [this message]
2022-01-16 23:31 ` bug#50374: " Nicolas Goaziou

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://guix.gnu.org/

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

  git send-email \
    --in-reply-to=87wnngfwv9.fsf@rekahsoft.ca \
    --to=collin@rekahsoft.ca \
    --cc=50374@debbugs.gnu.org \
    --cc=zimon.toutoune@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/guix.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).