1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024 <2025> | Index | 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024 <2025> |
<== Date ==> | <== Thread ==> |
---|
Subject: | Re: Converting Application using sumo |
From: | "Johnson, Andrew N. via Tech-talk" <tech-talk at aps.anl.gov> |
To: | Jörn Dreyer <j.dreyer at hzdr.de>, "tech-talk at aps.anl.gov" <tech-talk at aps.anl.gov> |
Date: | Wed, 19 Mar 2025 17:44:23 +0000 |
Hi Jörn, Your sample doesn’t match what our equivalent parts of the DEPS.DB file looks like. You appear to have registered several of the AreaDetector submodules as different versions of the same
"AREADETECTOR_3-14" module, and unless this is something supported in a newer (or much older) version of Sumo than we’re using (4.3) then that’s probably wrong. I’m attaching the AreaDetector parts of our DEPS.DB file for you to compare. Note that all the URLs are bogus, we have our own GitLab server where we import all the support modules we use locally, make local
modifications, and create our own tags. We have a “main” or “master” version for each of these modules that checks out the latest code, plus tagged versions (I only included one of each of them). Our version of the top-level AreaDetector module includes both the ADCore and ADSupport submodules, which is why they appear in the “extra” lists to be added to the dependent modules RELEASE files and don’t
have their own database entries. HTH, - Andrew -- Complexity comes for free, Simplicity you have to work for. |
Attachment:
AD-Deps.db
Description: AD-Deps.db