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  November 2013

QSERV-L November 2013

Subject:

Re: Demande de support pour eups

From:

Jacek Becla <[log in to unmask]>

Reply-To:

General discussion for qserv (LSST prototype baseline catalog)

Date:

Tue, 26 Nov 2013 21:23:04 -0800

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (83 lines)

Hi Fabrice,

Nice work!

I suspect you already have it on your to-do, but
since I'm looking at your package, I'll mention it:
it'd be good to avoid relying on hardcoded paths:
  * /home/fjammes/tmp/pkgroot in eups/startup.py
  * /opt/lsst/eups/bin/setups.sh in eups/env.sh

Perhaps we could just grab (as the very first step)
eups/bin/setups.sh from Robert's
https://github.com/RobertLuptonTheGood/eups ?

Thanks,
Jacek



On 11/26/2013 02:10 AM, Fabrice Jammes wrote:
> Hello,
>
> Here's a minimalist tutorial on how to use eups to distribute a package :
> https://dev.lsstcorp.org/trac/wiki/EupsTutorial/HowToDistrib
> Lots of things are still missing, so I'll continue improving it as i'll
> learn more about eups.
>
> Nevertheless, although eups code is clear and understandable and Paul
> Price offered me a very efficient support, i think i've met some bugs in
> eups.
> So in a first time i will confirm this and then possibly submit tickets.
>
> Have a nice day,
>
> Fabrice
>
>
> On 11/22/2013 02:35 PM, Christian Arnault wrote:
>> Bonjour Fabrice,
>>
>> j'avais produit une page wiki montrant un exemple de construction d'un
>> package utilisant le stack :
>>
>> <http://lsst.in2p3.fr/wiki/index.php/Utilisation_de_la_cha%C3%AEne_EUPS_%2B_scons>
>>
>>
>> ça ne couvre pas tous besoins (loin s'en faut) mais ça peut aider à
>> démarrer...
>>
>> je suis intéressé à poursuivre ce petit tutoriel avec toi (avec l'aide
>> des gens des US en cas de trou!)
>>
>> Cordialement
>> Christian
>>
>>
>> Le 22/11/2013 14:30, Fabrice Jammes a écrit :
>>> Bonjour à tous,
>>>
>>> SLAC m'a demandé de packager Qserv avec eups, or la création de
>>> paquet avec cet outil est très peu documenté.
>>> Connaitriez-vous une personne compétente sur l'utilisation de cet
>>> outil ?
>>>
>>> Merci et bonne journée,
>>>
>>> Fabrice
>>
>>
>
> ########################################################################
> 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
>

########################################################################
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