From: John Soo <jsoo1@asu.edu>
To: DA41336D-0210-44D7-8238-42D427260622@asu.edu
Cc: guix-devel@gnu.org
Subject: Re: Packaging FreeCAD
Date: Fri, 11 Jan 2019 11:42:12 -0800 [thread overview]
Message-ID: <24962B54-531C-44EE-BC12-AE875F96528C@asu.edu> (raw)
In-Reply-To: <9418631ae4add0fedd683d35db1e9bf8bc523e16.camel@tourbillion-technology.com>
Hey Paul,
I did not know Debian changed their version of opencascade. I will have to double check that they are using OCCT for FreeCAD still.
- John
> On Jan 11, 2019, at 1:35 AM, Paul Garlick <pgarlick@tourbillion-technology.com> wrote:
>
> Hi John,
>
> This is good news indeed for Guix-using engineers and architects. I
> shall follow developments with interest.
>
> I can look after the OpenCASCADE dependency too. This package is due
> an update but upstream development has been slow of late. Debian have
> switched to the OCCT version for FreeCAD and I am thinking that it
> would be best for Guix to follow suit. This would entail the
> introduction of a new opencascade-occt package, which I plan to do
> soon, if no-one beats me to it!
>
> Best regards,
>
> Paul.
>
>
>
next prev parent reply other threads:[~2019-01-11 19:42 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-11 9:35 Packaging FreeCAD Paul Garlick
2019-01-11 19:42 ` John Soo [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-01-14 12:42 Paul Garlick
2019-01-15 23:38 ` John Soo
2019-02-14 15:18 ` John Soo
2019-02-15 17:20 ` Paul Garlick
2019-02-15 18:33 ` John Soo
2019-03-10 2:14 ` John Soo
2019-03-10 7:25 ` Efraim Flashner
2019-03-12 15:15 ` John Soo
2019-05-09 13:50 ` John Soo
2019-05-28 20:21 ` John Soo
2019-05-30 16:23 ` Paul Garlick
2019-05-30 17:23 ` John Soo
2019-05-30 23:23 ` Paul Garlick
2019-06-18 8:27 ` John Soo
2019-06-18 18:11 ` Gábor Boskovits
2019-06-18 20:33 ` John Soo
2019-06-18 21:03 ` Paul Garlick
2019-06-19 14:12 ` John Soo
2019-06-30 2:45 ` John Soo
2019-01-09 16:18 John Soo
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=24962B54-531C-44EE-BC12-AE875F96528C@asu.edu \
--to=jsoo1@asu.edu \
--cc=DA41336D-0210-44D7-8238-42D427260622@asu.edu \
--cc=guix-devel@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).