[En-Nut-Discussion] Moving to Subversion

[Tim DeBaillie]

Does this include the malloc boundary bug fix?

Tim

--

Tim DeBaillie


On Dec 21, 2008, at 5:58 AM, Harald Kipp <harald.kipp at egnite.de> wrote:

> Hi all,
>
> As soon as remaining bugs in 4.7 are fixed, I will create a new branch
> 4.8 to get a new stable release published.
>
> As suggested by Thiago and others, we may finally take the chance and
> move the resulting CVS HEAD 4.9 to a Subversion repository. I do have
> some SVN experience (egnite is using it internally for some time), but
> not with the Sourceforge implementation. And I never converted a  
> project
> from CVS to SVN. Anyway, some hints had been posted in this list and
> I'll probably find more in the web.
>
> While moving, we may be able to solve another problem, which is caused
> by the current directory structure. When using the GNU autotools for  
> the
> first time, conflicts appeared.
>
> The source tree nut became the top directory when running 'make
> distcheck'. This introduced conflicts with existing files, which had
> been solved by renaming files or moving them to lib/. The remaining
> problem is, that the Linux/OS X user must manually create a new top
> directory, install the distribution in that directory and manually
> create a link (e.g. linking nut to ethernut-4.6.4).
>
> I'd suggest the following new structure
>
> trunk/
>  nutos/
>    nut/
>      app/
>      arch/
>      ...
> tags/
> branches/
>
> with nutos as a new top level directory containing the configure  
> script
> etc. and the existing source tree nut/ in a subdirectory.
>
> This way we will get the same top level structure when installing  
> Nut/OS
> on different platforms
>
> ethernut-x.y.z/
>  nut/
>  nutapp/
>  nutbld/
>
> Comments?
>
> Harald
> _______________________________________________
> http://lists.egnite.de/mailman/listinfo/en-nut-discussion
>