[lug] Structuring Mercurial projects (kinda off topic)

Jeffrey Haemer jeffrey.haemer at gmail.com
Tue Mar 30 09:35:29 MDT 2010


Before I offer irrelevant opinions, I'll ask for one clarification: a quick
google shows Mercurial as having branches.  Am I mislead by what I see, or
are you talking about something else?  No point in my trying to answer the
wrong question.

I know I branch and merge in git at the drop of a hat -- much more than in
SVN or CVS -- and I have the impression that's universal practice.

On Tue, Mar 30, 2010 at 9:16 AM, Michael J. Hammel <
mjhammel at graphics-muse.org> wrote:

> The HW guys at work have asked me to help them structure their source
> trees for new and ongoing hw projects.  We're using Mercurial and all
> dev is being done on Linux boxes.  I have one structure in mind but was
> wondering if anyone who's working on multiple hardware projects would
> view such a structure.
> Top level Mercurial projects:
> JTAG: debugger config files, CPLD, etc.
> System Build:  cross-compiler, bootloader, rootfs
> Kernel:  Linux versions specific to various boards
> Libraries:  User space
> VHDL: VHDL, FPGA and Firmware related files
> Applications:  user space
> Test Tools:  developer tools not delivered to clients
> Metabuild:  packaging of deliverables from multiple other trees.
> I've already created the system-build tree and brought it up (the build
> works for the only board ready to use it). FWIW, it uses uboot and
> buildroot, with the latter split into the cross compiler build and the
> rootfs build to avoid cross contamination during the builds and to avoid
> having to rebuild the xcc every time the rootfs is rebuilt.
> I'm curious if anyone has done something like this and how they deal
> with multiple boards in each tree.  Under CVS I would use, for example,
> Board1 and Board2 branches for the kernel development, JTAG or VHDL
> stuff.  Mercurial doesn't really have brances, as I understand it, so
> I'm not sure how branch structures would work under Mercurial.  I've
> never used git but suspect they do stuff like this all the time in the
> kernel dev trees.
> Any tips welcome.  Thanks.
> --
> Michael J. Hammel                                    Principal Software
> Engineer
> mjhammel at graphics-muse.org
> http://graphics-muse.org
> ------------------------------------------------------------------------------
> He doesn't have ulcers, but he's a carrier.
> -- From a real employee performance evaluation.
> _______________________________________________
> Web Page:  http://lug.boulder.co.us
> Mailing List: http://lists.lug.boulder.co.us/mailman/listinfo/lug
> Join us on IRC: irc.hackingsociety.org port=6667 channel=#hackingsociety

Jeffrey Haemer <jeffrey.haemer at gmail.com>
720-837-8908 [cell],  @goyishekop [twitter]
http://seejeffrun.blogspot.com [blog],
http://www.youtube.com/user/goyishekop [vlog]
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lug.boulder.co.us/pipermail/lug/attachments/20100330/3cb88a9d/attachment.html>

More information about the LUG mailing list