LISTSERV mailing list manager LISTSERV 16.5

Help for QSERV-L Archives


QSERV-L Archives

QSERV-L Archives


QSERV-L@LISTSERV.SLAC.STANFORD.EDU


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

QSERV-L Home

QSERV-L Home

QSERV-L  January 2014

QSERV-L January 2014

Subject:

Re: Qserv packaging with eups.

From:

"Daniel L. Wang" <[log in to unmask]>

Reply-To:

General discussion for qserv (LSST prototype baseline catalog)

Date:

Fri, 10 Jan 2014 12:31:31 -0800

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (45 lines)

On 01/10/2014 11:25 AM, Kian-Tat Lim wrote:
> The position I'd like to take is that we will figure out a way to make
> LSST Stack packages easily installable outside the Stack-standard
> environment.
This I would love. I'm really just trying to simplify development, and I 
see making stack packages easily installable as a task I'd rather not 
pick up, largely because the packaging system is still opaque to me.

> An alternative is that a "yum install" of qserv actually installs the
> Stack-standard environment, and that qserv lives within it.  Initially
> this seems less desirable, but it may not be if the environment
> installation is made lightweight enough.
Again, this is probably fine, but packaging up the stack environment 
into an rpm/deb feels kind of hard to me. But it might not be. It could 
be like installing pick-your-scripting-language's own package manager 
(which sysadmins sometimes accept, even as it annoys them).

> Having qserv go its own way to the extent that it cannot easily share
> code with the LSST Stack is simply unacceptable.
Philosophically, I agree. Even if LSST will perpetually use eups-managed 
LSST stack code, what you propose above (making packages easily 
installable outside the stack-std env) is immensely valuable.

A couple of possibilities: a python-lal (LSST Astronomical Library) 
package or a liblsstr (lsst runtime library, like libapr). This would 
make it easier for an open-source planetarium package that wants to 
reuse some algorithms. If possible, I think it's best if we have an eye 
to keeping things generic so our software plays well with everyone else, 
as long as being generic doesn't cost us too much in complexity.

Anyway, I have the (probably mistaken) impression that in order to reuse 
stack code, the normal way is that application X becomes a stack 
package, at least on the local machine. I'm sure the code is reusable 
more easily than that. I can write up some doc for how to do this and 
put it in a wiki page, as long as someone can give me the highlights and 
work with me. Sound okay?

-Daniel

########################################################################
Use REPLY-ALL to reply to list

To unsubscribe from the QSERV-L list, click the following link:
https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=QSERV-L&A=1

Top of Message | Previous Page | Permalink

Advanced Options


Options

Log In

Log In

Get Password

Get Password


Search Archives

Search Archives


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

March 2018
February 2018
January 2018
December 2017
August 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012

ATOM RSS1 RSS2



LISTSERV.SLAC.STANFORD.EDU

Secured by F-Secure Anti-Virus CataList Email List Search Powered by the LISTSERV Email List Manager

Privacy Notice, Security Notice and Terms of Use