oship-dev team mailing list archive

[Diego Manhães Pinheiro <me@xxxxxxxxxxxxxx>]

2010/9/15 Roger Erens <roger.erens@xxxxxxxxx>:
> Hi all,
>
Hi, Roger.
> I was going over the installation procedure as described in
> http://oship.org/docs/linux
>
> and I would like to propose to update it. Your comments please:
What a excellent idea!
Roger, do you mind execute this documentation update process ?
At the moment, our (OSHIP Development Team) focus and efforts are to
the OSHIP code evolution until 24th October, our milestone is finish
most important parts of openEHR reference model. Would be a great if
your schedule and effort allow work on this. If you accept, we can
help you on any problem that you find.
Since the installation procedure was modified, the documentation needs
update. I believe in a few weeks and a short time, this work can be
completed without gaps.
>
> 1)
> the pre-requisite of a C-compiler (i.e. build-essential on Ubuntu)
> should be mentioned
Agreed.
>
> 2)
> The work-around of installing mxdate by hand should be deleted.
Agreed.
>
> 3)
> The number of tests has increased a lot
Sorry, I didn't follow you. Why this is important to describe on the
documentation ?
What's your point here ?
>
> 4)
> Mentioning that an ImportError for the module _clips results from a
> missing C-compiler should be done in a Troubleshooting section, not in
> between the installation instructions.
Agreed.
I did a patch on PyCLIPS that I didn't send to appreciation by the
PyCLIPS project members yet. It just pieces of code changes that allow
install it with using the buildout system. This patch simplfies the
installation process.
>
> 5)
> This will imply some changes in the EpiS3 installation instructions, too.
I suppose so. :)
>
> 6)
> Eduardo's comment wrt pyxb can be removed?
Sorry, what comment ?
>
> 6
> When the new instructions are published, please confirm that they run
> on various OS's (I'm on Ubuntu 10.04 right now)
Until I know, It works on Windows, Ubuntu, CentOS, Debian and MacOSX.
I tested it carefully on all these systems when I update the
installation process.
Anyway, is important test again because I haven't been tested on all
these systems since the Grok was updated.
Just to remind: The buildbot running system is a Debian 4.0 (etch). In
my point of view, there isn't a valid argument that oblige us test it
again on this system.

If you are really looking forward on this, we can cover all system
types. I have access on Windows (just Seven 32bits), Ubuntu (10.04
64bits) and MacOSX( 32bits ) machines. I don't think be a problem for
me catch all systems requirements and describe how use our development
environment on these OSes.

Cheers
>
> Thanks,
>
> Roger
>
> _______________________________________________
> Mailing list: https://launchpad.net/~oship-dev
> Post to     : oship-dev@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~oship-dev
> More help   : https://help.launchpad.net/ListHelp
>