unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Arun Isaac <arunisaac@systemreboot.net>
Cc: 36043@debbugs.gnu.org
Subject: [bug#36043] [PATCH] Add Geany
Date: Wed, 19 Jun 2019 13:16:17 +0200	[thread overview]
Message-ID: <87fto5rfjy.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <cu7blyuhe4c.fsf@systemreboot.net> (Arun Isaac's message of "Wed, 19 Jun 2019 01:15:07 +0530")

Hello,

Arun Isaac <arunisaac@systemreboot.net> writes:

> This isn't particularly bad news. In that thread, Scintilla has agreed
> to allow an optional shared library build for people (like us) who
> really want it. But, the issue has been closed because it has been many
> years and no one has volunteered a patch.

Scintilla has agreed to allow an optional shared library if there is
also zero maintenance on their side (even when their ABI breaks). Since
this would eventually require maintenance, the submitter dropped
their request.

> I think we should go ahead with our unbundled shared library Scintilla
> package. We could also contribute our work upstream to Scintilla and
> they seem willing to accept it.

OTOH, using the static library is possibly (I failed at that, too)
straightforward, in the sense that we would not patch Scintilla. It is
worth considering this, too.

In any case, I do not volunteer to contribute our work upstream as it is
still above my pay grade.

> The wording of both these licenses are so similar that I would consider
> them to be effectively the same. But, I am not a lawyer, and I can't
> claim to know too much about copyright. Should we raise this question
> with guix-devel?

Scintilla's license has one more clause, but we can ask Guix devel.

> Note that some packages like gsl put the headers in /include/gsl because
> they are meant to be included, say as
>
> #include <gsl/gsl_vector.h>
>
> and not as
>
> #include <gsl_vector.h>
>
> So, the include headers install location is dependent on the package's
> conventions.
>
> As for nauty, their documentation specifies including as
>
> #include <nauty.h>
>
> So, the headers should be installed to /include.

OK. And what about the lib/, i.e., when should it be "/lib/name" instead
of "/lib/"

> Ok. Let's update our Scintilla package to 4.1.7. Shouldn't be a problem.

Indeed. Let's first sort out the issues around license (I'm going to
ask Guix devel about it) and bundling first.

Regards,

-- 
Nicolas Goaziou

  reply	other threads:[~2019-06-19 12:09 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-01 21:38 [bug#36043] [PATCH] Add Geany Nicolas Goaziou
2019-06-04 12:25 ` Arun Isaac
2019-06-05 21:01   ` Nicolas Goaziou
2019-06-06 14:45     ` Arun Isaac
2019-06-12 22:22       ` Nicolas Goaziou
2019-06-15  7:21         ` Arun Isaac
2019-06-17 20:29           ` Nicolas Goaziou
2019-06-18 19:45             ` Arun Isaac
2019-06-19 11:16               ` Nicolas Goaziou [this message]
2019-06-25  9:54                 ` Arun Isaac
2019-07-23 11:07                   ` Arun Isaac
2019-07-30  7:59                     ` Nicolas Goaziou
2019-07-30 11:38                       ` Arun Isaac
2019-07-30 18:04                         ` bug#36043: " Nicolas Goaziou
2019-06-06 14:51     ` [bug#36043] " Arun Isaac

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=87fto5rfjy.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --cc=36043@debbugs.gnu.org \
    --cc=arunisaac@systemreboot.net \
    /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).