Re: Fis-gtm accepted in unstable

["Bhaskar, K.S" <ks.bhaskar@fisglobal.com>]

Luis --

It might be helpful if you looked at one of my VistA SemiVivA packages (for an example, go to https://sourceforge.net/projects/worldvista-ehr/files/WorldVistA%20EHR%20_VOE%201.0/WorldVistA%20EHR%20_VOE%201.0%20Release%206-2008/ - shortcut at http://tinyurl.com/lgq32vh - look at the readme and download the release WorldVistAEHRVOE10Release6-08SemiVivA.tgz.nc from that page).  Installing VistA on a system is not like, say, installing an office suite where everyone runs the same software, or installing a web server, where one web server can serve all domains from that machine.  It's not even like a database engine, where you can create multiple database environments which the installed engine runs.

Instead, an installed VistA on a system is a source environment from which to build working environments, which are incrementally customized in both routines and state.  This is what a SemiVivA attempts to do.  From the installed environment, a script (which is called "install") creates a working environment, and also can create sub-environments off working environments, e.g,. for development and testing.

A SemiVivA includes a bundled GT.M.  That of course a VistA Debian package would not have.  Instead, it would depend on an fis-gtm meta-package, which would be satisfied by the package of any GT.M release.

Regards
-- Bhaskar

In my opinion, VistA should be packaged as a collection of .m source files, and

On 12/29/2013 06:31 PM (US Eastern Time), Luis Ibanez wrote:

On Sun, Dec 29, 2013 at 4:51 PM, Andreas Tille <andreas@an3as.eu> wrote:

Hi Luis,

On Sun, Dec 29, 2013 at 03:47:33PM -0500, Luis Ibanez wrote:
> 3) Added the "debian" subdirectory with the initial
>     sketch of what was done in
>
>
>       https://github.com/luisibanez/debian-med-vista
>
> I will now continue the packaging process by working
> exclusively on the vista git repository in Alioth.

thanks for your work on this.  I fixed the version number (to reflect
the version of the orig-tar) as it was commited as pristine-tar.  I also
fixed the package names which are not allowed to contain upper case
letters.

Andreas,

Thanks for fixing the version numbers and the package name.

I wasn't quite sure how to go about them.

 

I tried to build using the resulting packaging but it failed since
"source" is unknown.  If you really need to use bashisms you need to
Build-Depend from bash (but using `. $(yourscript)` would be better if
it is no real bash script.

My apologies for not warning you that the package was not quite

building yet. I still have some work ahead to update the full build process.

Just wanted to share the small steps of progress...

I'll look at removing the use of bash script.

 

I also think that

  gtm_dist=/usr/lib/fis-gtm/V5.5-000_x86_64

Is wrong since we packaged V6.x.  I think it would be more flexible to
not depend from a certain fis-gtm version or otherwise Build-Depend from
the needed version and in d/rules detect what verison is installed.

Yes,

I'll update this as well.

 

   Regards,

       Luis

 

-- 
GT.M - Rock solid. Lightning fast. Secure. No compromises.

_____________
The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you.