If some toolchain has an issue with hyphen separated name, then it should be solved in scope of that toolchain.
In particular, instructions for that particular toolchain should suggest different clone name as a workaround. One broken toolchain should not lead to violating of URL naming standards. On Sat, 19 Nov 2022, 15:53 Thiago Costa de Paiva, <t...@cpaiva.me> wrote: > From these, the valid argument is that it would be non-standard (not a top > level name) related to Appache rules, which I think is indeed not > acceptable. It would not imply any source code organization change nor > submodules: > > git clone <appache url>/nuttx/core nuttx > git clone <appache url>/nuttx/apps apps > > Anyway, from all the discussion, since hyphens should not be used > according to what Greg said previously, I think we have only two options: > > nuttx > nuttx_apps > > and > > nuttx > nuttxapps > > Thiago > > > 2022/11/19 15:37:21, Tomek CEDRO: > > Short answer: NO :-) > > > > Long answer: > > 1. This is not how current source code is organized. Implies > > additional work and will break compatibility. > > 2. There will be a problem with git repository. This may not be > > accepted by Apache or will require additional non-standard work that > > will not align with how other projects are organized. Top level names > > should be used. Using nuttx.git is fine but having apps.git among > > other projects will be confusing (what apps are these?). Also might > > imply using git submodules. There was a discussion about that and this > > seems unnecessary complication. > > > > Best regadrs :-) > > Tomek > > > > > > On Sat, Nov 19, 2022 at 3:28 PM Thiago Costa de Paiva <t...@cpaiva.me> > wrote: > > > > > > I am not attached to the name itself, I was just trying to solve the > problem with special characters. Would the following work? > > > > > > nuttx/core > > > nuttx/apps > > > > > > > > > 2022/11/19 08:21:43, Gregory Nutt: > > > > On 11/19/2022 8:12 AM, Gregory Nutt wrote: > > > > > We need to verify, but I do not think that the Apache github > repository > > > > > supports directories > > > > > > > > > > Technically, NuttX is NOT a kernel in most build modes. A kernel > is a > > > > > very specific architectural implementation involving protected > > > > > resources: https://en.wikipedia.org/wiki/Kernel_(operating_system) > . > > > > > The Linux kernel is a kernel. NuttX can be a kernel in the > protected > > > > > and kernel build modes, but in general, NuttX is not a kernel so > any use > > > > > of kernel in the naming would be wrong in most cases. > > > > > > > > > > https://en.wikipedia.org/wiki/Kernel_(operating_system) > > > > > > > > > > More correctly Linux (and NuttX in protected and kernel modes) is a > > > > > monolithic kernel. > > > > > > > > > > Even worse usage is when NuttX is occasionally called a micro > kernel > > > > > which is most certainly is not. A microkernel is an architectural > > > > > alternative to a monolithic kernel: > > > > > > > > > > https://en.wikipedia.org/wiki/Microkernel > > > > > > > > According to > > > > > https://en.wikipedia.org/wiki/Operating_system#Types_of_operating_systems > , > > > > NuttX in the flat build mode could be called a "library operating > system" > > > > with regard to memory organization. It is also a real-time, > multi-tasking, > > > > embedded operating system using those definitions. > > > > > > > > > > > > > > -- > > > Thiago Costa de Paiva > > > FSF member: 11963 > > > Linux User: 565327 > > > > > > > > > -- > > CeDeROM, SQ7MHZ, http://www.tomek.cedro.info > > > > -- > Thiago Costa de Paiva > FSF member: 11963 > Linux User: 565327 > >
