On Sat, Mar 30, 2013 at 12:31:10PM +0100, Martin Baehr wrote:
> can you describe the differences? 

I didn't implement it in rBuilder in the first place so I have never
known everything involved, so the first step is to figure it out.

I simply don't know.

> the commandline tool makes images but not installers?

Exactly.  It can create images, and optionally build tarballs of
their content, but doesn't know anything about how to combine
that with anaconda to build an installable image.

> or what is missing from the commandline tool to produce the same images
> as rbuilder?

Everything beyond building a tarball.

You can look at the build.log files on fdev for some of the steps
it takes; there all the command lines that are executed are logged.
That does not, however, include the steps of converting the
anaconda-templates and anaconda-custom packages into the template
into which rBuilder places the tarball.  I simply don't know yet
how that works, and I don't know how much investigation it will
take.

Yes, I was being a bit flippant (though honest!) when I said that
I'd welcome patches to implement this.

But really, I'd like to understand what it's doing, and then work
out the pieces that we *don't need*, and implement only what we
need, probably trying to use a workflow much closer to what upstream
anaconda does rather than the "make it easy to customize anaconda
without touching it" approach that rPath was trying to implement
and which is the source of several layers of indirection that I
now get to learn in order to remove them.  :)

I had already said in the mail to which you were responding that
it was my goal to implement that.

If it had been trivial, I would have done that first.  It was what
I had hoped to do in the first place.  But not doing the small hack
to make things work on the way to making them better would have been
silly given how old our current images are.

_______________________________________________
Foresight-devel mailing list
[email protected]
https://lists.foresightlinux.org/mailman/listinfo/foresight-devel

Reply via email to