From: "Ludovic Courtès" <ludo@gnu.org>
To: Ekaitz Zarraga <ekaitz@elenq.tech>
Cc: "40492@debbugs.gnu.org" <40492@debbugs.gnu.org>
Subject: [bug#40492] [PATCH] gnu: Add meshlab
Date: Mon, 27 Apr 2020 10:03:19 +0200 [thread overview]
Message-ID: <87r1w9we2g.fsf@gnu.org> (raw)
In-Reply-To: <YdoNZvfmmw6JlomYc7wYN4yeGV0RViJHsG0Bgzg60yF5ghS0cItwPNuE8-_YoJroxVl6Rpw93EnHLXc3dsel1AxzMFbBfhLV2M2Z4IQrLMk=@elenq.tech> (Ekaitz Zarraga's message of "Sun, 26 Apr 2020 21:00:09 +0000")
Saluton,
Ekaitz Zarraga <ekaitz@elenq.tech> skribis:
> PS: Should I push those to the same file under engineering? or should I create a new file for meshlab and add all its dependencies there too?
You can add the new packages in the file where it makes most sense,
which may or may not be engineering.scm.
Thanks for looking into it!
Ludo’.
next prev parent reply other threads:[~2020-04-27 8:04 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 [this message]
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
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=87r1w9we2g.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=40492@debbugs.gnu.org \
--cc=ekaitz@elenq.tech \
/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).