All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakob Hirsch <jh@plonk.de>
To: mlmmj@mlmmj.org
Subject: Re: exim4
Date: Sun, 13 Mar 2005 23:55:30 +0000	[thread overview]
Message-ID: <4234D2F2.3090601@plonk.de> (raw)
In-Reply-To: <4232593D.2000404@plonk.de>

Mads Martin Joergensen wrote:

>>I've wondered about that myself. If the binaries are installed somewhere
>>in $PATH, wouldn't that provide sufficient method for finding them?
> I would prefer for security reasons not to start parsing environment
> variables. 

Sounds sensible, but mlmmj uses execvp, which uses PATH itself, so why 
should you have to parse that yourself?
Another possibility would be to use a hard coded path from configure or 
some header file.

 > Besides, with this method, you can have many mlmmj
> installations in parallel.

mlmmj uses no config file, so what's the use? Having different versions 
of mlmmj running? That should be done with configure's --program-suffix. 
Otherwise you end up having a directory for every mlmmj installation.

  parent reply	other threads:[~2005-03-13 23:55 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-12  2:51 exim4 Jakob Hirsch
2005-03-12 13:42 ` exim4 Mads Martin Joergensen
2005-03-12 14:36 ` exim4 Drake Wyrm
2005-03-12 20:04 ` exim4 Mads Martin Joergensen
2005-03-13 23:48 ` exim4 Jakob Hirsch
2005-03-13 23:55 ` Jakob Hirsch [this message]
2005-03-14  8:55 ` exim4 Mads Martin Joergensen
2005-03-14  8:56 ` exim4 Mads Martin Joergensen
2005-03-14  9:29 ` exim4 Christian Laursen
2005-03-14  9:30 ` exim4 Morten K. Poulsen
2005-03-16 11:42 ` exim4 Jakob Hirsch
2005-03-16 11:55 ` exim4 Jakob Hirsch
2005-03-16 11:58 ` exim4 Mads Martin Joergensen
2005-03-16 12:16 ` exim4 Jakob Hirsch
2005-03-18 13:40 ` exim4 Mads Martin Joergensen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4234D2F2.3090601@plonk.de \
    --to=jh@plonk.de \
    --cc=mlmmj@mlmmj.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.