On Tuesday, 5 November 2024 21:22:14 CET Lonnie Cumberland wrote:
On a side question regarding ham, I did try to create a "~/l4re" directory and then did the ham init from within there thinking that it might put all of the L4Re related directories under that initial sub-directory, but it did not and put them under my base home directory. Is there some cli switch or flag that I can use to have ham put everything in the l4re sub-directory and build in there instead. This is not critical, but mostly just to keep all of the l4re stuff together and in one sub-directory for good housekeeping, I guess?
The way I tend to use ham is to put its repository inside my equivalent to your l4re directory. Having built the tool, I ascend to the top-level directory (your ~/l4re directory) and run the tool like this:
ham/ham init -u https://github.com/kernkonzept/manifest.git ham/ham sync
This creates the fiasco and l4 repository hierarchies alongside the ham repository. I don't tend to run ham after that, but I don't really find it particularly approachable, anyway. I think I understand what problem it is trying to address (multi-repository versioning), but it needs more documentation and arguably more consistency with existing version control tools.
In any case, good luck with your L4Re investigations!
Paul
_______________________________________________ l4-hackers mailing list -- l4-hackers@os.inf.tu-dresden.de To unsubscribe send an email to l4-hackers-leave@os.inf.tu-dresden.de