Thanks for doing this.
Are you going to do the move on a copy of the repoistory and resubmit, or
just through normal cvs access? I would be reluctant for you to move mul in
a way that looses easy access to the file histories.
As to the best directory structure, I think it would be easier (for the
documentation robots, as well as ourselves) if each of contributed modules
stayed at the same relative directory level. So maybe have
FYI: We (Manchester) are planning a big code conversion job on our internal
code (Moving from mul to vil2) on the 25th November, and a final push to
optimise vil2 at the same time. I wouldn't have thought that you would have
any problem finishing by then.
> -----Original Message-----
> From: Amitha Perera [mailto:perera@...]
> Sent: Tuesday, November 12, 2002 1:42 AM
> To: vxl-maintainers@...
> Subject: Re: [Vxl-maintainers] vgui ascension
> I'll volunteer to do the vgui move this weekend, if there are no
> So: please don't commit anything after Thursday. I'll then
> email this list when I'm done.
> Hopefully all will be done by Monday.
> The only plan I have is to move oxl/vgui (back) vxl/vgui, renaming the
> currently empty vxl/vgui to vxl/vgui.old.
> Should I move all the other libraries into "contrib", as Geoff
> suggested a while ago? If so, I will need some direction on the
> layout. One idea:
> Another option is to move vgui into contrib/gui/vgui. This may
> alleviate some of the concerns people have with building vgui. (That
> it's difficult and has many dependencies.) However, I don't like the
> idea of "half-core" libraries. We've discussed this before, and have
> always concluded that something is either "core" or not. I don't think
> vgui should be an exception.
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> Vxl-maintainers mailing list