It is my opinion that all package names should be lower case. Or case-insensitive. Having mixed-case case-dependent names just adds possibility for error without any gain. (I'm thinking about the hour I wasted debugging a CMake script this week over "BOOST" vs "Boost".)
-- Elizabeth On Mon, Jan 18, 2016 at 3:54 PM, Kenneth Hoste <[email protected]> wrote: > Hi Ben, > > On 18/01/16 21:25, Ben Roberts wrote: > >> Hi, >> >> At our facility a colleague of mine recently prepared some custom EB >> recipes for FFmpeg (https://www.ffmpeg.org). A little later I found >> easyconfigs for ffmpeg [sic]. I imagine case is important in Easybuild, and >> it’s at least good to be consistent. It seems the official name is FFmpeg. >> Is it worth updating the name, or better on the whole to stick with the >> status quo? >> > > Typically, we try and stick to the 'official' software name, indeed. > Sometimes it's hard to tell, but here it's pretty clear: it should be > 'FFmpeg' (cfr. https://www.ffmpeg.org/about.html). > > So, yes, changing it to FFmpeg makes sense to me. I see this as a bug fix. > > This has some impact though, especially because 'ffmpeg' is currently used > as a dependency for 'animation' and 'OpenCV'. > In the PR where the current 'ffmpeg' are changed to use 'FFmpeg' instead, > the dependency specs will need to be updated too (if not, Jenkins will > complain about failing unit tests). > > The only issue with this rename is that this potentially impacts > easyconfig files that are not included in the central easyconfigs > repository: if they use 'ffmpeg' now, they will need to be changed to use > 'FFmpeg' (unless the required 'ffmpeg' easyconfigs are also available > locally). > In this case, the impact is likely low though... > > > regards, > > Kenneth >
