On Fri, Sep 7, 2012 at 10:24 AM, Angus Gratton
<[email protected]> wrote:
Hi everyone,
I'm curious about how people manage paths in RELEASE, like EPICS_BASE,
ASYN, etc.
I've been using paths relative to the respective TOP, of this kind:
EPICS_BASE=$(TOP)/../../base
But when upgrading to 3.14.12.2 (from 3.14.11), convertRelease.pl
decided these were invalid (3 line patch attached that allows this by
canonicalising any path that exists at check time, any chance of this
please being accepted into base? )
The App Developer's Guide shows RELEASE with absolute paths
arranged under /home/epics, but surely this doesn't scale across
multiple developers or multiple working copies?
So it all made me wonder - how does everyone else do it?
- Angus
Index: base/src/tools/EPICS/Path.pm
===================================================================
--- base/src/tools/EPICS/Path.pm (revision 1268)
+++ base/src/tools/EPICS/Path.pm (revision 1269)
@@ -123,6 +123,9 @@
# Now calculate the absolute path
my $abs = File::Spec->rel2abs($path, abs_path($cwd));
+ if (-e $abs) {
+ $abs = abs_path($abs);
+ }
return LocalPath($abs);
}
