[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#553311: python-ldraw



On Sat, 10 Mar 2012 18:58:46 +0100, David Boddie wrote:

> On Saturday 10 March 2012, David Paleino wrote:
> 
> [..]
> 
> > > Checking now, it seems that the parts library described at
> > >
> > >   http://www.ldraw.org/Downloads-req-viewdownloaddetails-lid-98.html
> > >
> > > is not redistributable because it contains non-redistributable parts.
> >
> > This is not a problem: the non-redistributable parts can be stripped from
> > the "original tarball", which can then be used (and distributed) by Debian.
> 
> I see LeoCAD itself has its own parts library, mentioned here:
> 
>   http://leocad.org/trac/wiki/Legal
> 
> Whether or not it's preferable to use that library is not something I can
> help with, unfortunately. It might make it slightly easier to repackage if
> it does not contain non-redistributable parts to start with, but the file
> format question remains.

Well, I downloaded leocad's parts library, and.. they're precompiled binary
files:

$ ls /tmp/pieces-5243/
pieces.bin    pieces.idx    sysfont.txf   textures.bin  textures.idx

I'd expect these were compiled from some .dat (and possibly other files?).
We need to find out how :)

> [...]
> 
> > So, here's the current status. LeoCAD now builds fine, so the only missing
> > bit is the pieces library. I/we need to find out what the real source is
> > (if it's not the .dat files), how to compile it, and what leocad expects it
> > to be (location, format, structure, [..]).
> 
> My impression is that the LDraw format used in .dat files is the common
> currency, if not the nicest format to edit, and that at least some part
> authors actually write it by hand. All the parts in the official parts
> database (http://www.ldraw.org/cgi-bin/ptlist.cgi) are in that format, as
> far as I can tell. Where you would go to find those files in another format
> is unclear.
>
> I presume that part authors who don't actually write parts by hand use many
> different tools to create them before submitting them to the database as
> .dat files.

Here's another point: to be an acceptable form of "source", we'd need some
software in Debian (main) capable of creating/manipulating those .dat files.
Expanding the comparison to fonts, we have "fontforge" which nicely behaves
with .ttf (not sure about .sfd). So, even if they're binary files, they are
actually the source.

I hope the situation's a bit clearer now :)
David

-- 
 . ''`.   Debian developer | http://wiki.debian.org/DavidPaleino
 : :'  : Linuxer #334216 --|-- http://www.hanskalabs.net/
 `. `'`  GPG: 1392B174 ----|---- http://deb.li/dapal
   `-   2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174

Attachment: signature.asc
Description: PGP signature


Reply to: