>
> I have a trac 'related' question, although it is primarily a
> Subversion/philosophy question.
>
> I am on a project that has 2 very distinct parts.


We've done similar things, where we have broken it down like so (this is a
big example):

trunk/board1/vhdl
trunk/board1/c
trunk/board1/c_eth
trunk/board1/matlab
trunk/board1/schematics
trunk/board1/schematics/datasheets
trunk/board2/vhdl
trunk/board2/schematics
trunk/board2/schematics/datasheets
trunk/board3/vhdl
trunk/board3/schematics
trunk/board3/schematics/datasheets
trunk/sbc_src/
trunk/control/src
trunk/control/manual
lib/c
lib/matlab
lib/vhdl

Board 1 has an FPGA with an embedded PPC (C code in .../c) and an embedded
ethernet microcontroller (C code in .../c_eth). Boards 2 and 3 are FPGAs
only (with layout & schematics). Then there's the embedded Linux single
board computer, whose C code is in sbc_src. Finally, the control front end
(which happens to be in VBA embedded in Excel-ACK!) sits in control/src with
documentation in control/manual.

This way all the code is in one project, but you can just "deep checkout"
with svn if you only need one section. And you can easily branch something
like "control" without affecting other code (for example if you were trying
to write a C version instead of VBA). Almost every source directory has an
svn:external pointing to the lib that is applicable, e.g. trunk/board3/vhdl
has an external pointing to lib/vhdl .

Hope this helps.

  Aaron

Glossary ;)
http://en.wikipedia.org/wiki/Datasheet
http://en.wikipedia.org/wiki/FPGA
http://en.wikipedia.org/wiki/Schematic
http://en.wikipedia.org/wiki/VHDL
http://en.wikipedia.org/wiki/Visual_Basic_for_Applications

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To post to this group, send email to trac-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/trac-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to