unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
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: Mon, 11 May 2020 14:10:42 +0000	[thread overview]
Message-ID: <Bo3u1lRCje7tHGzqmpRZYQMT8tCow8k4GO7fQzotBC8sneLBTDRe3b3YsaYJqzTU_feR4T9Kc91b5DHBpoxWu9o567uok0W8U1Bg_2TO750=@elenq.tech> (raw)
In-Reply-To: <87a72eiqu9.fsf@gnu.org>

Kaixo,


On Monday, May 11, 2020 2:44 PM, Ludovic Courtès <ludo@gnu.org> wrote:

> Egun on!
>
> > 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.
>
> Ideally, yes. Now, if some of these libraries have no other users, we
> can make an exception.

Understood.
Weird stuff like openkinect is not going to be used anywhere else, right? :D

> > 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?
>
> We could still unbundle for example qhull and, if needed, package that
> older version that Meshlab need. In parallel, we can report the issue
> to the Meshlab developers so that future versions can use the current
> qhull.

Ok!

> I realize this is quite some work, so you’re welcome to improve things
> incrementally. If you don’t manage to deal with all the bundled
> libraries, then you can still send an updated patch and we’ll see where
> we are and perhaps push the version you arrived at.

I attach what I currently have. It's a working package with most recent version of Meshlab (overwrites older patch) with some of the libraries unbundled. It has some extra comments about bundled libs that may be better to remove if it's released, but I'll leave that to your opinion.

I'll keep doing this because it's important for me. Meshlab is a very powerful tool and we almost have it!

ty,

Ekaitz




  reply	other threads:[~2020-05-11 14:15 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
2020-05-11 12:44                   ` Ludovic Courtès
2020-05-11 14:10                     ` Ekaitz Zarraga [this message]
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='Bo3u1lRCje7tHGzqmpRZYQMT8tCow8k4GO7fQzotBC8sneLBTDRe3b3YsaYJqzTU_feR4T9Kc91b5DHBpoxWu9o567uok0W8U1Bg_2TO750=@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).