From: Ekaitz Zarraga <ekaitz@elenq.tech>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: "40492\\@debbugs.gnu.org" <40492@debbugs.gnu.org>
Subject: [bug#40492] [PATCH] gnu: Add meshlab
Date: Sun, 10 May 2020 21:29:35 +0000 [thread overview]
Message-ID: <5Xe04GEft3Gf5wO_7lIfdvvkO2Vt2ow9ykrLBPWOxgnkYRCbbLl1fdhPmdc2iO6JL8ZMyQA6zRGlz_7I1Hi-4DrrdnR9HySNCVrxj3ZI3R0=@elenq.tech> (raw)
In-Reply-To: <v-XKa6UjWGoRVnQcUI1iQIoa2Sm0rG8x6Vq-lMKKZy9veBMKa0FvYxbO-SH43iEezQRtZR3Cjp5wPhbA5RIwxPJhuFnSjGcrV6Boz8s1E50=@elenq.tech>
Hi,
> Not yet :(
>
> I'll try to get some free time these days but I've been busy.
> Is it possible to add it like it is with embedded libraries temporarily until we separate all of them?
I'm working on it. I managed to add some system provided libraries but I'm having issues with qhull and I'm trying to fix them upstream.
First step, I filed an issue in meshlab: https://github.com/cnr-isti-vclab/meshlab/issues/678
Second step will be to fix the issue.
Next I need to figure out what to do with the rest of the libraries. Should we package all of them? Some of them don't look interesting by themselves, maybe it's better to keep them bundled.
I also have a question:
Most of the libraries that are bundled in meshlab have very old versions (qhull's version is from 2003). How does Guix handle breaking changes in libraries?
If meshlab doesn't support newer libraries, what do we need to do?
I'll manage to correct qhull's issue and submit a new patch.
Thanks!
next prev parent reply other threads:[~2020-05-10 21:29 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-07 17:08 [bug#40492] [PATCH] gnu: Add meshlab Ekaitz Zarraga
2020-04-22 17:23 ` Ludovic Courtès
2020-04-22 18:40 ` Ekaitz Zarraga
2020-04-22 19:52 ` Ludovic Courtès
2020-04-25 19:47 ` Ekaitz Zarraga
2020-04-26 20:49 ` Ludovic Courtès
2020-04-26 21:00 ` Ekaitz Zarraga
2020-04-27 8:03 ` Ludovic Courtès
2020-05-08 14:30 ` Ludovic Courtès
2020-05-08 14:30 ` Ludovic Courtès
2020-05-08 14:47 ` Ekaitz Zarraga
2020-05-10 21:29 ` Ekaitz Zarraga [this message]
2020-05-11 12:44 ` Ludovic Courtès
2020-05-11 14:10 ` Ekaitz Zarraga
2020-05-11 14:11 ` Ekaitz Zarraga
2020-05-14 8:06 ` Ludovic Courtès
2020-05-14 8:17 ` Ekaitz Zarraga
2020-05-15 22:41 ` Ekaitz Zarraga
2020-05-21 11:59 ` Ekaitz Zarraga
2020-06-12 16:13 ` Ludovic Courtès
2020-06-12 16:32 ` Ekaitz Zarraga
2020-06-12 19:45 ` Ludovic Courtès
2020-06-12 21:46 ` Ekaitz Zarraga
2020-06-13 14:58 ` bug#40492: " Ludovic Courtès
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='5Xe04GEft3Gf5wO_7lIfdvvkO2Vt2ow9ykrLBPWOxgnkYRCbbLl1fdhPmdc2iO6JL8ZMyQA6zRGlz_7I1Hi-4DrrdnR9HySNCVrxj3ZI3R0=@elenq.tech' \
--to=ekaitz@elenq.tech \
--cc=40492@debbugs.gnu.org \
--cc=ludo@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/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).