oship-dev team mailing list archive

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

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Em 21/09/10 05:52, Roger Erens escreveu:
> On Fri, Sep 17, 2010 at 00:48, Diego Manhães Pinheiro <me@xxxxxxxxxxxxxx> wrote:
>> 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 ?
> 
> Of course not, that's why I started this thread.
I'll create a blueprint and assign it you, OK? It is not my intention
make pressure on it, on contrary : blueprint allows everybody knows
what's going on, and who is working on each part of the process. If
anybody wants to help on this part of the work, it will know who is
behind of it, allowing help you and reducing the work size you will do.
> 
>> 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.
> 
> Great!
> 
>> 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 ?
> 
> I think Tim slipped this into the documentation to show newcomers that
> OSHIP is 'well-behaved' in the sense that we try to test as much as
> possible. Or at least we have the intention to do so :-)
> When he wrote that phrase the command $ bin/test resulted in 28 tests
> passing. When I last checked it was well over 100 (from the top of my
> head).
> But on the other hand, as you rightly question the use of it, it
> breaks the flow of installing a little, and this section might move to
> some more advanced piece of documentation (e.g. for developers).
> 
>>>
>>> 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.
> 
> Thanks for doing so; much less hassle now.
> 
>>>
>>> 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 ?
> 
> At the bottom of the page he added this comment:
> You can install PyXB via buildout by running:
> easy_install 'http://pypi.python.org/pack[…]d308c4c23c79e050dd0d323172f'
Ok. Yes, it can be removed. I did a patch which allows install it with
buildout too. At the moment, the installation process use the version
that I patched to install it easily.
All these versions can be found at : http://newton.iff.edu.br/oship .
Tim said that we can upload the python egg files on the OSHIP website,
but haven't do it yet.
> 
>>>
>>> 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.
> 
> Did you mean: 'As far as I know'?
Exactly.
> 
>> 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.
> 
> And testing again is also important when the documentation changes
> substantially :-)
> 
> 
>> 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.
> 
> I don't understand what you mean.
> It's tested nightly, or after every commit, hence no need for us to test it?
> Or do you want to change the OS for buildbot?
If we want support some OSes, it's important find a way to preserve
assurance on these systems. Buildbot can help a lot on this process. At
the moment, there is a unique kind of O.S. that run tests on the
buildbot, which is a Debian 4.0 Linux. In my opinion is unnecessary test
the OSHIP on this system again, because every time a code commit is sent
to the launchpad trunk VCS repository, a test process are triggered.
Maybe in future, we could add different systems to the run on the
buildbot system, in order to preserve the work garantee.
> 
>>
>> 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 think it would be nice indeed to have a little table showing on
> which OSes OSHIPpy installs smoothly.
> 
>> I don't think be a problem for
>> me catch all systems requirements and describe how use our development
>> environment on these OSes.
> 
> I'm sorry, again I don't understand what you mean. You still are
> referring to installation?
Yes.
> Maybe as a first step we can concentrate on 1 mainstream OS (Ubuntu
> 10.04 32bit) and then add the extra info for other OSes.
OK, that's right. Anyway, when OSHIP gonna be tested on other operating
systems that I described, I can help you because I have access to
different systems.
> 
> Roger

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (Darwin)

iQEcBAEBAgAGBQJMmQ/1AAoJEEfarWn4YOc8C9IIAM3sg706kxToTk8EbZEqtB1B
PQUkA46MIHQCVQAPO7QZ5Iy2EfO+tku9gx0J85Qrps44oZ/u5GUn2uWMBQRBozix
p879qBlfKVfr7phpJe2ximA+OJEn8SzImqCXgwquG3sKH/W8EbxXPavyQv5z35U+
vsbKg0EtFjMmi/TLjYohbJUvI1H5Nrlu8ii5TmWMpyHW3kJGG10rjEvDF4J8zEYy
7Kt9lbFua0/KP8y13ay1VhJnrudxZpuL0rP9QI3UYZF+GkvBs4fZ+EMhug0WxDpv
fwVRbfTydP/8X7MpXrmMEiYUA//DNO8vWA23E4CkcKn7eD9vxn81lKoLvLws1k8=
=440l
-----END PGP SIGNATURE-----