Bug#841104: ITP: cspice -- C implementation of The SPICE Toolkit

[Walter Landry]

Rock Storm  wrote:
> On Fri, 2016-11-04 at 17:23 -0700, Walter Landry wrote:
>> I replaced the build system with waf.  I have a waf package already.
>> Waf is a bit controversial in Debian, so I need to make an ITP and see
>> what the Debian consensus is.
> 
> I completely ignore waf and how it works, but I'll take a look at it,
> it seems promising.

FYI, I filed my waf ITP.

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843325

For reasons I do not understand, it has yet to show up on
debian-devel.

> Even though it is a pain and feels outdated I was sticking to
> upstream's build system, I'd rather modify the source as little as
> possible.

In case it helps, I am attaching a Makefile that builds using the
upstream build system.  It is for a specialized setup we have here,
but should work with minor tweaks.  It does not build shared
libraries.

> As soon as the licensing issue is cleared up I'll upload my progress in
> case you'd like to review it and/or collaborate.

Are you in contact with upstream?

Cheers,
Walter Landry
INSTALL = install
INSTALL_PROGRAM = $(INSTALL) -m 755 -p
INSTALL_DATA = $(INSTALL) -m 644 -p
INSTALL_DIR = $(INSTALL) -m 755 -d

prefix=$(shell cd ../..; pwd)
exec_prefix=$(prefix)
bindir=$(exec_prefix)/bin
libdir=$(exec_prefix)/lib
includedir=$(prefix)/include/cspice
datadir=$(prefix)/data

all:  installdirs
if [ ! -d cspice/ ] ; then \
tar -xf dist/cspice.tar.Z ; \
else true ; \
fi
cd cspice; ./makeall.csh
$(INSTALL_PROGRAM) cspice/exe/* $(bindir)
rm -rf $(datadir)/*
$(INSTALL_DATA) cspice/data/* $(datadir)
rm -rf $(includedir)/*
$(INSTALL_DATA) cspice/include/* $(includedir)
$(INSTALL_DATA) cspice/lib/* $(libdir)
# symlink cspice.a to libcspice.a, the usual name for a library
ln -f -s cspice.a $(libdir)/libcspice.a 

installdirs :
$(INSTALL_DIR) $(bindir) $(libdir) $(includedir) $(datadir)

install:
true

clean:
rm -rf cspice/

Bug#841104: ITP: cspice -- C implementation of The SPICE Toolkit

[Rock Storm]

On Fri, 2016-11-04 at 17:23 -0700, Walter Landry wrote:
> Here is a tarball.
> 
>   https://caltech.box.com/s/f64t26xgauc9re6k3sryv5spagipslnu

Thanks for sharing. I'm examining it to see what can be drawn upon.

> I replaced the build system with waf.  I have a waf package already.
> Waf is a bit controversial in Debian, so I need to make an ITP and see
> what the Debian consensus is.

I completely ignore waf and how it works, but I'll take a look at it,
it seems promising. Even though it is a pain and feels outdated I was
sticking to upstream's build system, I'd rather modify the source as
little as possible. 

As soon as the licensing issue is cleared up I'll upload my progress in
case you'd like to review it and/or collaborate.

Thanks again,
Rock

Bug#841104: ITP: cspice -- C implementation of The SPICE Toolkit

[Walter Landry]

Rock Storm  wrote:
> On Mon, 2016-10-31 at 14:02 -0700, Walter Landry wrote:
>> FYI, I created a package for this for my own use.
> 
> That's awesome! Is it uploaded somewhere? Could you share it with me? I
> would love to take a look at it.

Here is a tarball.

  https://caltech.box.com/s/f64t26xgauc9re6k3sryv5spagipslnu

As promised, the package is not optimal.  It is versioned with git,
but the modifications to debian/ and the main package are mixed.  If
DEBFULLNAME and DEBEMAIL are set, then running

  fakeroot debian/rules binary

should give you three rpms

  cspice_0065-1_amd64.deb
  libcspice-dev_0065-1_amd64.deb
  libcspice_0065-1_amd64.deb

I replaced the build system with waf.  I have a waf package already.
Waf is a bit controversial in Debian, so I need to make an ITP and see
what the Debian consensus is.

Cheers,
Walter Landry

Bug#841104: ITP: cspice -- C implementation of The SPICE Toolkit

[Walter Landry]

Rock Storm  wrote:
> On Mon, 2016-10-31 at 14:02 -0700, Walter Landry wrote:
>> FYI, I created a package for this for my own use.
> 
> That's awesome! Is it uploaded somewhere? Could you share it with me? I
> would love to take a look at it.

I can share it.  Give me a day or so.  The build is ... complicated.

>> It is pretty terrible, but if I find the time, I may be able to make
>> a proper package.  If you already have a proper package, yours is
>> probably better.
> 
> I've been busier than I expected so I haven't done much yet, probably
> merging our efforts is the best option.

Ok.

> Nevertheless, I still have to discuss with legal whether distributing
> this package complies with the DFSG.

For what it is worth, I am a regular on debian-legal.  In this link

  
http://naif.jpl.nasa.gov/pub/naif/toolkit//C/PC_Linux_GCC_64bit/packages/README

I see a disclaimer, but no right to modify.  This link

  https://naif.jpl.nasa.gov/naif/rules.html

allows modification, but not simple redistribution?  To make things
even more muddy, this presentation

  
https://indico.esa.int/indico/event/111/session/27/contribution/130/material/slides/0.pdf

says that it is "free of licensing".

So it is pretty clear that we have to get a clarification on what,
exactly, the license is.  It looks like the person to talk to is the
NAIF manager at JPL.  His contact info is in the 'rules' link.
Clarifying this could, potentially, take a while.

Cheers,
Walter Landry

Bug#841104: ITP: cspice -- C implementation of The SPICE Toolkit

[Rock Storm]

On Mon, 2016-10-31 at 14:02 -0700, Walter Landry wrote:
> FYI, I created a package for this for my own use.

That's awesome! Is it uploaded somewhere? Could you share it with me? I
would love to take a look at it.

> It is pretty terrible, but if I find the time, I may be able to make
> a proper package.  If you already have a proper package, yours is
> probably better.

I've been busier than I expected so I haven't done much yet, probably
merging our efforts is the best option.

Nevertheless, I still have to discuss with legal whether distributing
this package complies with the DFSG.

-- 
Regards,
Rock

signature.asc
Description: This is a digitally signed message part

Bug#841104: ITP: cspice -- C implementation of The SPICE Toolkit

[Walter Landry]

FYI, I created a package for this for my own use.  It is pretty
terrible, but if I find the time, I may be able to make a proper
package.  If you already have a proper package, yours is probably
better.

Cheers,
Walter Landry
wlan...@caltech.edu

Bug#841104: ITP: cspice -- C implementation of The SPICE Toolkit

[Rock Storm]

Package: wnpp
Severity: wishlist
Owner: Rock Storm 

* Package name: cspice
  Version : 0065
  Upstream Author : NASA's Navigation and Ancillary Information Facility (NAIF)
* URL : http://naif.jpl.nasa.gov/naif/index.html
* License : public-domain
  Programming Lang: C
  Description : C implementation of The SPICE Toolkit

SPICE (Spacecraft Planet Instrument C-matrix Events) is a NASA ancillary 
information system used to compute geometric and event information in analyzing 
and planning science observations obtained from spacecraft. It is also used in 
planning missions and conducting numerous engineering functions needed to carry 
out those missions.

SPICE has become the de facto standard for handling much of the so-called 
observation geometry information on NASA's planetary missions, and it is now 
widely used in support of science data analysis on planetary missions of other 
space agencies as well. Some SPICE capabilities are used on a variety of 
astrophysics and solar physics missions, such as JAXA's Hayabusa project, ESA's 
Rosetta or NASA's Steins.

I would like this package to be maintained either by the Debian Astro team or, 
if it were outside its scope, the Debian Science team.

Regards,
Rock