Seeking source code management advice Show more
Seeking source code management advice Show more
@clacke Rosinstall seemed promising, but I wanted to avoid the dependency. I skimmed over wstool, but I should take a closer look.
(I'm still dealing with yocto and bitbake. Bitbake seems like clever idea taken too far: We'll just make everything a string combined with a framework that operates behind the scenes on those strings that does stuff. The relationship between the things in your strings and the actions they cause is not clear by inspection.)
@clacke Thanks for the links. I'll need to check those out. It's not a high priority, but I would definitely like to move away from Yocto if possible. The only reason I'm using it now is because upstream vendor (Freescale/NXP) used it. I now realize Yocto may help solve vendor's problems (and they can apparently afford the brittle complexity), but doesn't necessarily help solve small team, downstream OEM problems.
@clacke Oh, no worries. I took it that way. I'm in a collect research in the background mode on this topic anyway. So it's perfect. :)
@clacke @cstanhope @telent OMG, I'm very excited to see somebody building a NixWRT. I recently helped a client mangle NixOS into a static root file system builder for a different purpose, and while there are clearly some upstream changes that would help, it worked really nicely in a lot of ways. I'd love to see Nixpkgs/NixOS evolve into a Yocto replacement!
This looks useful enough!
github.com/vcstools/wstool/blo…
> wstool allows manipulation of a set of version-controlled folders as specified in a workspace definition file.
I looked at the alternatives and they all look either git-specific or tied to some specific project and project structure like yoctolinux (bitbake)(0) or ROS. Some want to own your layout and put things in some specific workspaces directory.
wstool, the one linked above, looks like it's rosinstall without the ROS dependency (just some vestigial config file naming).
I have a sudden urge to write a rosinstall2nix. Later! Not now!
(0) *shudder* bad memories from when I was battling bitbake 3 summers ago