From: Arun Isaac <arunisaac@systemreboot.net>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: 36043@debbugs.gnu.org
Subject: [bug#36043] [PATCH] Add Geany
Date: Tue, 25 Jun 2019 15:24:22 +0530 [thread overview]
Message-ID: <cu7wohaf0s1.fsf@systemreboot.net> (raw)
In-Reply-To: <87fto5rfjy.fsf@nicolasgoaziou.fr>
[-- Attachment #1: Type: text/plain, Size: 1624 bytes --]
>> 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.
I would prefer the shared library because it is more efficient on
memory/disk usage and it seems cleaner and more modular. However,
scintilla is a small library and is not used by too many packages,
therefore the advantages are small. Meanwhile, patching scintilla to
build a shared library is messy and using the static library would
indeed be easier. But, if we are using the static library, why should we
unbundle at all?
I don't know if Guix has a clear policy on these matters. I think we
should consult guix-devel and ask for others' opinions.
> In any case, I do not volunteer to contribute our work upstream as it is
> still above my pay grade.
No problem, I understand.
> Scintilla's license has one more clause, but we can ask Guix devel.
I guess we should use the hpnd license now, as discussed in guix-devel.
> And what about the lib/, i.e., when should it be "/lib/name" instead
> of "/lib/"
I don't have as good an answer for this. A quick look at my
~/.guix-profile/lib shows almost all packages having their shared
libraries in /lib, not in /lib/name. And, just including scintilla in
geany's inputs and passing '-lscintilla' in geany_LDFLAGS was enough for
the linker to find libscintilla.so correctly. So, I assumed I had done
it right. :-P
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2019-06-25 9:55 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
2019-06-25 9:54 ` Arun Isaac [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cu7wohaf0s1.fsf@systemreboot.net \
--to=arunisaac@systemreboot.net \
--cc=36043@debbugs.gnu.org \
--cc=mail@nicolasgoaziou.fr \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.