[Top][All Lists]

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

Re: [Gnumed-bugs] <bug>: 0.6.rc3 trying to print meds from VM, this

From: Jim Busser
Subject: Re: [Gnumed-bugs] <bug>: 0.6.rc3 trying to print meds from VM, this
Date: Fri, 01 Jan 2010 10:30:50 -0800

On 2010-01-01, at 9:27 AM, Karsten Hilbert wrote:

>> Well, its exists locally, but not in pycommon: 
>> address@hidden:~$ find ~ -name gm-print_doc*
>> /home/jbusser/gmrc/c0.6.rc3/client/doc/gm-print_doc.1
>> /home/jbusser/gmrc/c0.6.rc3/external-tools/gm-print_doc
>> /home/jbusser/gmcvs/gnumed/gnumed/client/doc/man-pages/gm-print_doc.1
>> /home/jbusser/gmcvs/gnumed/gnumed/external-tools/gm-print_doc
>> I was running from rc3. Will resolution be in rc4, or is this some problem 
>> originating at my end?
> gm-print_doc needs to be executable via the system PATH
> (IOW, it needs to be in one of the directories named in
> $PATH, for example /usr/local/bin/).

Does it make the most sense that, within GNUmed, such files (as for medication 
printing) reside in .../external-tools?

1. If so, would it be helpful and nontrivial that that running from tarball or 
cvs ( would dynamically and automatically append to the current 


residing at the same level as


without which it will forever be extra work for people who would download a 
tarball to get GNUmed to work (properly)

2. Pending any such adjustment, shall I just do it myself, locally?

3. Does the dependency mean that distribution managers should need to copy all 
such files into


and if so where should such instruction reside?

reply via email to

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