From: Marc Joliet <marcec@gmx.de>
To: Gentoo <gentoo-user@lists.gentoo.org>
Subject: Re: [gentoo-user] [OT] cura or (better!) cura ?
Date: Wed, 18 Oct 2017 22:12:58 +0200 [thread overview]
Message-ID: <4573288.rEEOLmFOya@thetick> (raw)
In-Reply-To: <20171018174433.rigcjgvhl4kmogc3@solfire>
[-- Attachment #1: Type: text/plain, Size: 1211 bytes --]
Am Mittwoch, 18. Oktober 2017, 19:44:33 CEST schrieb tuxic@posteo.de:
> Hi,
>
> what is the better choice:
> This one:
> * media-gfx/cura
> Available versions: (~)0.15.04.4 (~)0.15.04.5_rc5 (~)2.1.0_beta
> (~)2.3.1 (~)2.6.0 {+usb PYTHON_SINGLE_TARGET="python3_4 python3_5
> python3_6" PYTHON_TARGETS="python2_7 python3_4 python3_5 python3_6"}
> Homepage: https://github.com/Ultimaker/Cura
> Description: A 3D model slicing application for 3D printing
>
^^^^^^^^^^^
> or
> This one:
> * media-gfx/curaengine
> Available versions: (~)0.15.04.6 (~)2.1.0_beta (~)2.3.1 (~)2.6.0 {doc
> test} Homepage: https://github.com/Ultimaker/CuraEngine
> Description: A 3D model slicing engine for 3D printing
>
^^^^^^
> Looks pretty identical to me...but I am no native speaker... ;)
As I attempted to point out above, one is the engine and one is the
application. I suspect that installing cura will pull in curaengine as a
dependency (addendum: looking at the ebuild verified this).
> Cheers
> Meino
HTH
--
Marc Joliet
--
"People who think they know everything really annoy those of us who know we
don't" - Bjarne Stroustrup
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-10-18 20:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-18 17:44 [gentoo-user] [OT] cura or (better!) cura ? tuxic
2017-10-18 20:12 ` Marc Joliet [this message]
2017-10-19 11:28 ` Zhu Sha Zang
2017-10-19 23:02 ` Marc Joliet
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4573288.rEEOLmFOya@thetick \
--to=marcec@gmx.de \
--cc=gentoo-user@lists.gentoo.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox