[install-discuss] Re: Install and Packaging in Mercurial

[Paul Armstrong]

Glen Wrote:
> Somewhere underneath the plans to get the rest of the Install code
> capable of being open sourced.

This is why it's in it's own tree instead of part of onnv?

> Could you define 'very painful' for me? While I realize that the
> current build process for the packaging tools is highly sub-optimal and
> the term 'hack' comes to mind, it mostly just works in my experience.
> Are you running into any specific issues that we might be able to
> address short term?

It's mostly just a case of using an SCM versus not. Being able to 
do an update to the tree you're working on and mark collisions as it goes
(possibly even allowing you to fix them as it goes) instead of having to 
generate a patch, download the latest tarball, untar into a new
workspace and then see if the patch applies cleanly are considerably
different.

I've only just started looking at hacking Nevada code so this could
be just a document that I've not managed to find yet (finding that
Mercurial existed was a trial in of itself).

Thanks,
Paul
 
 
This message posted from opensolaris.org