K-T,
>> It's all very confusing to me, but my interpretation is that each
>> package version has its own manifest file and you can specify the
>> dependent packages and versions there. Is that correct?
> 	You don't create the manifest file yourself; eupspkg creates it
> for you as a result of running "eups distrib create".
>
>> Would you point me at a good example of a well
>> packaged/setup/manifest-included set of files that I can poke at on a
>> distribution server?
> 	You shouldn't need to look at such a set; any need to do so is a
> failure of the procedure, so I'd rather not.
You said:

"This all depends on how your distribution stack is setup and tagged. 
You can choose to have any set of versions (that is mutually compatible) 
in the distribution manifest."

But in python/eups/distrib/eupspkg.py, I can't see how to manipulate 
(and tag?) the distribution stack. There are some examples for creating 
a particular package with a version number, with source located 
<somewhere>, but it says nothing about dependencies, except "If foo has 
any dependencies, EupsPkg packages will be created for those as well." 
How does it know what versions of foo dependencies are needed? I suppose 
it could introspect and see what versions are "setup" or "current" at 
the time you ask it to "create". Does it do this?

I feel like what I want is somewhat in conflict with what eupspkg wants 
to provide:
I want to say: "Install package X, version A" and have the system 
respond "Oh, X depends on Y, version B. I will make sure Y version B is 
installed and then install X version A"
Whereas I feel like eupspkg is designed to allow an arbitrary 
combination of packages, i.e., it would respond "Oh, X depends on Y. Oh, 
you have Y version C installed. That's cool, I'll use that and just 
install X version A"

Thank you for being patient with me. Eups greatly confuses me, but maybe 
this discussion will help me become a little less confused.

-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