Page History

root for conda work: /reg/g/psdm/sw/conda

Right now, can't build things once that work on all OS's, so managing rhel[567], also, since you can do things that screw up conda itself, I want a devel and production installation of the two that are separate, makes for 6 miniconda installs 

Key subdirectories here:

• build - the condarc's will point to subdirs here for the minicondas: dev-rhel5  dev-rhel6  dev-rhel7  prod-rhel5  prod-rhel6  prod-rhel7
• channels - the channels
  • external-rhel[567] things like szip that we can't find in conda channels
  • system-rhel[567] openmpi that we have to build locally against lsf
  • psana-rhel[567] ndarray, psalg, pdsdata, psana, etc
  • there will be softlinks here like psana -> psana-rhel5 to suggest that our rhel5 builds will be what we export publicly
• develop - I modified conda from github and put it here, things like that, we are developing part of the conda system instead of using standard packages
• downloads - 
  • condapkgs - if we download conda packages directly, put them here, but we may just download them directly into the miniconda installls
  • miniconda - different downloads of the miniconda install startup script,  
  downloads - where we download packages that we will build our own conda recipes out of, or software to install, like miniconda itself, hdf5, openmpi, h5py
  • downloads/Miniconda2-2016* - we may download new versions of https://repo.continuum.io/miniconda/Miniconda2-latest-Linux-x86_64.sh, or start using the py3 version. Don't put those files in downloads, make a subdirectory with the date.
• miniconda2prod - where our production install of miniconda will be for users
• miniconda2devel - where a development install of miniconda will be for us to test things that affect the build system, like upgrading conda itself.
• manage
  • manage/recipes
  • manage/
• logs
• recipes
• scripts
• channels

...

• • otherpkgs - like hdf5 openmpi, ect
• envs
  • dev-rhel[567] and prod-[567], the condarc's will point the installs here
• inst  - this is where the miniconda installs will be
  • dev-rhel[567] and prod-rhel[567]
• logs - from all the builds. Filenames like conda_build_external_szip-2.1-0_rhel5_linux-64_00.log
  record channel, package, and OS. By default repeated builds increment the _00 at the end. 
• manage - software to manage, this is checked out in github. There is a readme with more recent info
  • config - template for condarc, tag files, etc?
  • pinned - soft links to the 'pinned' files that are in directories like envs/ana/conda-meta
  • recipes - recipes for packages we build locally
    • external - like our old external packages, but the ones that we'd rather not build ourselves, just doing it because we couldn't find a conda channel, or we wanted more control over the package build
      • szip-2.1 
      • guppy
    • psana
      • psalg
      • pdsdata
      • ndarray
      • psana - when we get around to it
    • system - anything that has system dependencies, like mpi, and then anything that depends on it, maybe we should roll this in with external?
      • openmpi
      • hdf5
      • h5py
      • mpi4py, etc
  • scripts the code that we run to help manage, in particular, the file
    • ana-rel-manage - just give it -h to see what to do
• sandbox - scratch stuff to test things out, like figuring out rpath, etc
• test - after activating a conda environment, do python run_tests.py from here.