Daniel,
> > You always get current for dependencies unless you say
> >otherwise.
> Is there anyway to eliminate that (for a local stack)? I think Jacek
> and I would be much less confused if eups never tried to setup
> "current". Maybe a flag or option we could pass?
> > You need to do this with "-t tag" or have current defined
> >properly or use "-j" or, preferably, "-k".
-t tag always gets you versions tagged with that label. This is
the usual way Stack developers operate, I believe.
-j never changes any of your already-setup dependencies.
-k doesn't change any dependencies setup with "-r".
> What I'm slowly learning is that an eups "tag" means a particular
> combination of component package versions. So the right thing for
> qserv is to stamp an eups tag across all packages that qserv depends
> on, for each merge to master on qserv.
Ideally, this is what buildbot does. You should use the
appropriate buildbot tags (bNNN).
> So, all qserv devs need to have the appropriate privileges and
> knowledge to do this, hence the process and the philosophy need to be
> documented.
We all agree that process and philosophy documentation are
sorely lacking.
--
Kian-Tat Lim, LSST Data Management, [log in to unmask]
########################################################################
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
|