hello,
I am not favorable personally with submodules. They are a pain to keep
in sync across multiple remotes and branches.
This was used in the past in NuttX, and it was aborted.
Sebastien
On 12/13/19 3:28 AM, Anthony Merlino wrote:
I think submodules are a good way to go. That would leave us with 3 repos
as the core Apache NuttX. One for 'nuttx' which, is Greg suggests, should
always be exclusively the OS. One for 'apps'. And one for "linking" them
together, and for providing other NuttX infrastructure that may not be
appropriate in the core OS repo.
[image: photo]
*Anthony Merlino*
CTO & Co-founder, Verge Aero
(609)-319-1399
On Thu, Dec 12, 2019 at 8:17 PM David Sidrane <david.sidr...@nscdg.com>
wrote:
How about sub modules? We atomically tag across both to keep the project in
proper synchronization.
David
-----Original Message-----
From: Nathan Hartman [mailto:hartman.nat...@gmail.com]
Sent: Thursday, December 12, 2019 10:55 AM
To: dev@nuttx.apache.org
Subject: Re: Project Emails
On Thu, Dec 12, 2019 at 1:36 PM Gregory Nutt <spudan...@gmail.com> wrote:
A NuttX release consists of two tarballs nuttx/ and apps/. nuttx/ is the
operating system proper; apps/ is a collection of applications that may
or maynot be used with the operating system proper. These applications
including some key things and I think most people want to incorporate
some subset of applications into their project.
But since the applications are NOT part of the operating system they do
need to remain separate. I would argue against trying to merge
application code into the operating system. So I think we have to
consider these two separate releases. We historically release them
together as a matched pair so that the use can be user that they
interoperate properly.
+1 : I agree that nuttx and apps should stay separate.
That begs the question, are we going to have two separate Git
repositories? Because Git lacks support for multiple projects in one
repository. (There's nothing in Git that prevents you from trying, but
Git does not have the features that make the "monorepo"/"megarepo"
pattern work; e.g., it does not have sparse/partial working copies or
clones. Trying to combine nuttx and apps into one repository would
force everyone to clone a lot of content they may not need/want and
which may complicate building the RTOS with only their custom
applications.)
Nathan
