Hi Ernest,
On Thursday 30 October 2008 09:12:23 Ernest L. Williams Jr. wrote:
>
> After a site deploys the official release point, then patches can be
> obtained via another scheme.
> For example, in the Known Problems area on your web site. Should there
> also be a version string change?
> Something like, 3.14.10-p1.
Not in the official release version...
> Maybe, it's better for each site to handle
> the version after the release point on their own since
> they will most likely make some local changes.
> That's why you guys created "EPICS_SITE_VERSION" ?
Precisely. The combination of patches that you've applied and other local
changes you've made is always going to be unique to your site, so if you want
to be able to distinguish between site-specific versions that variable lets
you do so. You should of course document those changes somewhere as well,
although if you keep everything in a source code repository you can at least
do the equivalent of a 'cvs log' to find out what you changed.
HTH,
- Andrew
--
Talk is cheap. Show me the code. -- Linus Torvalds
- References:
- Re: EPICS R3.14.10 version number Andrew Johnson
- Re: EPICS R3.14.10 version number Ernest L. Williams Jr.
- Navigate by Date:
- Prev:
Re: EPICS R3.14.10 version number Ernest L. Williams Jr.
- Next:
Re: errlogVprintf does not print messages to console Andrew Johnson
- Index:
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: EPICS R3.14.10 version number Ernest L. Williams Jr.
- Next:
Re: errlogVprintf does not print messages to console Andrew Johnson
- Index:
2002
2003
2004
2005
2006
2007
<2008>
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
|