On Fri, Nov 29, 2013 at 08:38:18AM +0000, Paul Sherwood wrote:
On 29/11/2013 08:12, Rob Taylor wrote:
>> > I get an interesting issue running check --full on my fedora 18 system:
>> that is interesting, but i think the normal use-case is to run it on
> I would say a couple of things to this.
> 1) it seems to still be a bug, even if its not currently exhibited on a
> current baserock systems
It may well be bug, but one of the things we're trying to avoid for now
is getting sucked into issues regarding baserock components on
non-baserock systems. We're a tiny team, as you know...
> 2)I think there's a value in being able to develop morph on
I think I disagree, but I'm only one voice.
It's not an insurmountable proposition.
Morph is runnable on any Linux system that has python 2.7 and a few
python libraries, though we'd probably end up having to package those
ourselves if we need new enough versions of cliapp for example.
morph can build on any system with a recent enough kernel that it supports
linux-user-chroot and has git available.
You can even get away without having gcc on the system if you don't need
to touch build-essential.
Most of the extra dependencies we add to our Baserock systems are to
support deployment, but we could theoretically build those dependencies
as well and deploy from a chroot.
The biggest issue I see with using morph on your host system is that we
currently require building as root. This is ok on an isolated development
VM, but morph is complicated and most people probably wouldn't feel safe
running it with sudo.
Deploying without root will be significantly more difficult, since
creating disk images is a priviliged operation, but those individual
commands could be run with sudo, and there are tools for creating disk
images without mounting, but they tend to be more primitive than we need
them to be.
> Especially as I find current baserock develop systems a
> little unpleasant to use as a development environment (in particular,
> missing man pages and some odd behaviour from vim)
Yup - we have plenty of room for improvement on developer experience :)
I see using Baserock as the development systems as an important Dogfooding
exercise, and as soon as we have some engineering time for it, I'd like
to see us running Baserock on bare-metal with all the nice things expected
of a Linux distro.
However, if we're going to give up Baserock as a Linux distro, then I
think it would make sense to put effort into getting morph working on
other distros, since people deploying to devices will already have their
own deployment scripts, which may require distro specific tools.
tl;dr: it's not a massive amount of work to build on other distros,
but we don't have the engineering to do that and have our own distro.