Hi Lewis,
> Or maybe Git submodules should be avoided. It seems to me that there
> are a number of headaches related to the use of submodules in EPICS Base
> that come up from time to time; now it has come up in areaDetector, and
> I suspect the headaches will continue simply because submodules add
> complexity.
> I think a Git repo containing all of EPICS Base and another
> one containing all of areaDetector would be much simpler to deal with.
> I'm not a fan of submodules in general.
I think you are mixing up 2 very separate issues:
1) Having multiple repositories for EPICS base or areaDetector
2) Using git submodules to link those repositories
In my opinion it would be a terrible idea to go back to having areaDetector be a single git repository, which is how it was before R2-0. By having multiple repositories we can independently release the core code (ADCore), the supporting libraries (ADSupport), and each detector (ADPilatus, etc.). This is essential to producing timely releases.
The use of git submodules in areaDetector is completely optional for the end-user. They can simply checkout out each repository independently and manually arrange them in the following hierarchy
areaDetector
ADCore
ADSupport
ADPilatus
etc.
The use of "git clone --recursive" is not required. It is just a convenience if people want to check out lots of modules at the same time.
In areaDetector only areaDetector repository and the ADCore repository are released synchronously, i.e. they have the same tags. All other modules are released independently and have different tags. So it really does not make sense to check out R3-2 at the top-level and expect it to update the submodules to some specific release (except ADCore).
Mark
> -----Original Message-----
> From: [email protected] [mailto:[email protected]] On
> Behalf Of J. Lewis Muir
> Sent: Monday, February 05, 2018 12:23 PM
> To: Jörn Dreyer <[email protected]>
> Cc: [email protected]
> Subject: Re: AreaDetector repository inconsistent
>
> On 02/05, Jörn Dreyer wrote:
> > if I remember correctly I have seen this problem sometime ago
> > already. Maybe someone should look into implementing a commit hook
> > that prevents such situations.
>
> Or maybe Git submodules should be avoided. It seems to me that there
> are a number of headaches related to the use of submodules in EPICS Base
> that come up from time to time; now it has come up in areaDetector, and
> I suspect the headaches will continue simply because submodules add
> complexity. I think a Git repo containing all of EPICS Base and another
> one containing all of areaDetector would be much simpler to deal with.
> I'm not a fan of submodules in general.
>
> Lewis
- Replies:
- Re: AreaDetector repository inconsistent J. Lewis Muir
- References:
- AreaDetector repository inconsistent Jörn Dreyer
- Re: AreaDetector repository inconsistent Ralph Lange
- Re: AreaDetector repository inconsistent Jörn Dreyer
- Re: AreaDetector repository inconsistent J. Lewis Muir
- Navigate by Date:
- Prev:
Re: AreaDetector repository inconsistent Ralph Lange
- Next:
Re: TDK Lamda Genesys EPICS IOC Heinz Junkes
- 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
- Navigate by Thread:
- Prev:
Re: AreaDetector repository inconsistent Ralph Lange
- Next:
Re: AreaDetector repository inconsistent J. Lewis Muir
- 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
|