For a long time, we've been limited in what names we can give our releases because Spack can't handle path lengths beyond 127 characters. In fact, we're bumping right against the limit - the base release in our candidate releases has a name like rc-v4.3.0-2 rather than rc-dunedaq-v4.3.0-2 because of this limit. Similarly, in this GitHub Action for the purposes of demonstration I tried making a nightly release with the name NABABCDEFG24-01-16 and it didn't work - meaning a nightly release with a name such as NAOFFLINE24-01-16 also wouldn't work.
So how should we reduce the length? Let's look at the immediate parent directory of last night's far detector nightlies:
You can see that both spack-0.20.0 and gcc-12.1.0 appear twice in the path. So one option would be to simply drop the spack-0.20.0-gcc-12.1.0 subdirectory, and we'd have:
For a long time, we've been limited in what names we can give our releases because Spack can't handle path lengths beyond 127 characters. In fact, we're bumping right against the limit - the base release in our candidate releases has a name like
rc-v4.3.0-2rather thanrc-dunedaq-v4.3.0-2because of this limit. Similarly, in this GitHub Action for the purposes of demonstration I tried making a nightly release with the nameNABABCDEFG24-01-16and it didn't work - meaning a nightly release with a name such asNAOFFLINE24-01-16also wouldn't work.So how should we reduce the length? Let's look at the immediate parent directory of last night's far detector nightlies:
You can see that both
spack-0.20.0andgcc-12.1.0appear twice in the path. So one option would be to simply drop thespack-0.20.0-gcc-12.1.0subdirectory, and we'd have:another would be to simply rename
spack-0.20.0-gcc-12.1.0togcc-12.1.0:These seem to be the two reasonable choices, in fact.