From: John Soo <jsoo1@asu.edu>
To: Paul Garlick <pgarlick@tourbillion-technology.com>
Cc: guix-devel@gnu.org
Subject: Re: Packaging FreeCAD
Date: Tue, 15 Jan 2019 15:38:29 -0800 [thread overview]
Message-ID: <908E44F3-8ECE-466E-91A9-AE2AB4C8DCB7@asu.edu> (raw)
In-Reply-To: <4071518a081f8bdf5b119dc774d9876ba8d5bd7b.camel@tourbillion-technology.com>
Hi Paul,
Thank you for saving me the headache! I’ll keep this posted with progress.
- John
> On Jan 14, 2019, at 4:42 AM, Paul Garlick <pgarlick@tourbillion-technology.com> wrote:
>
> Hi John,
>
>> I did not know Debian changed their version of opencascade
>
> There are two versions of OpenCASCADE in Debian, named 'liboce' and
> 'libocct'. 'occt' is the upstream variant, 'oce' is the community
> maintained variant. Historically, Debian has switched between the two
> as licence requirements dictated.
>
> Currently, both are packaged and FreeCAD version 0.17 depends on
> liboce. However, libocct is being more actively maintained and I
> believe the intention for Debian FreeCAD version 0.18 is for the
> dependency to switch to libocct.
>
> Best regards,
>
> Paul.
>
next prev parent reply other threads:[~2019-01-15 23:38 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-14 12:42 Packaging FreeCAD Paul Garlick
2019-01-15 23:38 ` John Soo [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2019-01-11 9:35 Paul Garlick
2019-01-11 19:42 ` 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=908E44F3-8ECE-466E-91A9-AE2AB4C8DCB7@asu.edu \
--to=jsoo1@asu.edu \
--cc=guix-devel@gnu.org \
--cc=pgarlick@tourbillion-technology.com \
/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).