[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: Karsten Hilbert
Subject: Re: [Gnumed-bugs] <bug>: 0.6.rc3 trying to print meds from VM, this
Date: Fri, 1 Jan 2010 19:49:09 +0100
User-agent: Mutt/1.5.20 (2009-06-14)

On Fri, Jan 01, 2010 at 10:30:50AM -0800, Jim Busser wrote:

> > 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?

That is where we deliver them inside the tarball, yes. Since
we cannot know where distributions will want to put them we
make clear what they are - tools external to the GNUmed
client proper.

> 1. If so, would it be helpful and nontrivial that that running from tarball 
> or cvs ( would dynamically and automatically append to the 
> current PATH
>       .../external-tools
> residing at the same level as
>       .../client

I have been thinking about how to do that. There is no
clear-cut answer. People may want to install/use tarballs
while still using their very own gm-print_doc in
/usr/local/bin or even ~/bin/ or some such. They may not
want/have kprinter but rather prefer something else while
the default will "always" come with kprinter.

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

Well, once, really, unless the requirements/capabilities of
the gm-print_doc solution changes.

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

It might be a good idea to add (prepend !)
/home/jbusser/bin/ to your PATH and put your gm-print_doc
there. I have done the same (well, mine is a link to my CVS
copy but I expect that link to be stable on my machine,
probably not so on yours).

> 3. Does the dependency mean that distribution managers should need to copy 
> all such files into
>       /usr/local/bin

Yes, or rather wherever they see fit within the context of
their distribution. But, yes, that belongs to their tasks.
Come to think of it the file lacked instructions to that
effect ... ;-)

GPG key ID E4071346 @
E167 67FD A291 2BEA 73BD  4537 78B9 A9F9 E407 1346

reply via email to

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