(hoping to reach you here -- the mcad mailing list looks so
as with openscad, i intend to package mcad for debian; users who install
openscad would automatically get openscad-mcad as well (it is
recommended, and thus installed automatically on most systems).
there are some issues that keep me from finishing the package, and i
hope we could work them out here:
* is there a plan to get some form of release / -numbering? while i can
go for date based snapshots, i'd prefer to have something you claim to
be stable or at least "considered for release" (or alpha version, or
* copyrights are a bit messy -- there are files that claim a license but
no copyright holder (among them the README), files with a copyright
holder but no license statement, and some under-specified licenses
(like "creative commons"; detailed below).
could you clarify that? (e.g., if the authors of polyholes.scad and
teardrop.scad agreed to have the files published under LGPL2.1, note
that in the files.)
* py.test fails quite some tests (starting with docs where it expects
README instead of REAME.markdown); is it supposed to be up to date?
* Package name : openscad-mcad
Version : 0 (unreleased yet)
Upstream Author : quite a bunch
* URL : http://reprap.org/wiki/MCAD * License : LGPL2.1 (and some more)
Programming Lang: OpenSCAD
Description : library for the OpenSCAD 3D modeling software
The MCAD library is a collection of modules and functions for OpenSCAD. It
contains boxes, gears, screws, and several generic shapes.
The library is a kind of a standard library for OpenSCAD.
the package is technically ready, but quite a mess on the copyright
side; plus, upstream has not yet decided how to do releases. i'm
packaging it anyway as it will be included in the next openscad release
(itp bug 583476), and i stripped it out in favor of a Recommends: to
with copyright, there are several issues:
* the "base library" (the library is really just a collection of useful
files) doesn't clearly state an author. (although it can be deduced
from git logs and package website.)
* some files don't mention original copyright holders (constants.scad,
math.scad). i'd be tempted to attribute them to the base library
author, but then why should they use another license? (plus, the base
library author's other files are cleanly labelled.)
it could be argued that they don't reach the required threshold of
originality, but i'd have to ask -legal about the implications of
* some files don't mention licenses, just copyright (polyholes.scad,
* some files mention incomplete licenses ("Creative Commons" is not a
license (involute_gears.scad), neither is "BSD" (boxes.scad), and
neither "public domain" (at least where i live, but at least it is
clear what the author means; trochoids.scad))
for the time being, a basic package is uploaded at debian mentors.
> * is there a plan to get some form of release / -numbering?
..and a version which can be queried at run-time would rock.
This is implemented in OpenSCAD-master atm.:
o The version() function will return the OpenSCAD version as a vector, e.g. [2011, 09]
o The version_num() function will return the OpenSCAD version as a number, e.g. 20110923
On Sun, Oct 30, 2011 at 6:49 AM, Whosawhatsis <[hidden email]> wrote:
> I don't have access to the repo, but I wrote the teardrop.scad file and
> released it as LGPL. If the maintainer could add the appropriate license
> message for me, I would appreciate it.
> Also, looking back at it, I noticed a typo in the comment at the beginning.
> Where I wrote "Rotation around Y or Z will cause the angle to be wrong",
> that should of course the X or Y, not Y or Z.
I've added the LGPLv3 preamble to teardrop.scad and fixed the typo.
If anyone has any pull requests, patches, or would like commit access
to the git repo, let elmom or I know.