health-dev
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Health-dev] GNU Health Mercurial repository at Savannah


From: Cédric Krier
Subject: Re: [Health-dev] GNU Health Mercurial repository at Savannah
Date: Tue, 13 Sep 2011 11:38:28 +0200
User-agent: Mutt/1.5.21 (2010-09-15)

On 13/09/11 06:03 -0300, Luis Falcon wrote:
> 2011/9/13 Cédric Krier <address@hidden>
> 
> > On 13/09/11 05:30 -0300, Luis Falcon wrote:
> > > 2011/9/12 Cédric Krier <address@hidden>
> > >
> > > > On 12/09/11 16:04 -0300, Luis Falcon wrote:
> > > > > 2011/9/12 Cédric Krier <address@hidden>
> > > > >
> > > > > > On 12/09/11 05:45 -0300, Luis Falcon wrote:
> > > > > > > Let me know if you find any issues .
> > > > > >
> > > > > > How could I know for which Tryton version is it?
> > > > > >
> > > > > > We could use the version variable in __tryton__.py  that matches
> > > > current
> > > > > Tryton version. This is very specific to Tryton, keeping the
> > "generic"
> > > > > version number for other apps, like Android.
> > > >
> > > > But will it not introduce missunderstanding for the user when he will
> > see
> > > > different version number per example on the website and in the module
> > list
> > > > in
> > > > the client?
> > > >
> > > It shouldn't. We can specify it in the file name though.
> >
> > I don't understand.
> >
> > You can have it in the file name ( tar.gz ) specifying the Tryton version.
> The current format today is gnuhealth.major.minor.build.<app>.tar.gz
> 
> So in <app> today we have tryton. Here I could add the version number of the
> Tryton server, so gnuhealth.1.3.2.tryton2.0.tar.gz
> 
> We use the minor number to specify development (odd numbers) vs stable (
> even ).

Indeed I don't realy care about the file naming.

What I see is that you want to keep a separate numbering for GNUHealth that
doesn't include the Tryton series. And that's fine. So you must show this
number also in the __tryton__.py file to keep concistant.
But for someone who is installing GNUHealth, he must know the list of
dependencies of the packages and this must be done in the "Python world" with
a setup.py script which contains install_requires. And in this setup script it
must have as requirements something like:

    'trytond >= 2.0, < 2.1'

So I think the zodman's patch is a good starting point but there is some
issues that needs to be fixed like:

    - what is the download page
    - keep the GNUHealth numbering
    - define the package naming ("trytond_medical_xxx")


This brings me to a new question how do we contribute?

-- 
Cédric Krier

B2CK SPRL
Rue de Rotterdam, 4
4000 Liège
Belgium
Tel: +32 472 54 46 59
Email/Jabber: address@hidden
Website: http://www.b2ck.com/

Attachment: pgpufTm4hss5u.pgp
Description: PGP signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]