DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:mime-version:in-reply-to:references:date
	:message-id:subject:from:to:content-type; q=dns; s=default; b=Zv
	EdbVISNJEpK01ve3CBLK9niam4cmg39fSBocAT+tw1YhRlkSAopDEO9tDmsbu+80
	t850anihleB93eqB/AkhsY3aCs4Kdb6YEmDj0b2PJcKni/fHvgkhhKvWsNj1eKJL
	qry1jerQv9OUgtCO2siJkXkQTcOM5+cPdOTg5d9pM=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
MIME-Version: 1.0
In-Reply-To: <816144.8551.bm@smtp119.sbc.mail.ne1.yahoo.com>
References: <54137C7F.1040507@redhat.com>	<541415B1.8090500@t-online.de>	<541698CC.7090802@lysator.liu.se>	<5416F946.7010905@t-online.de>	<20141008134106.GF29235@calimero.vinschen.de>	<5435714D.6060206@t-online.de>	<20141009100317.GI29235@calimero.vinschen.de>	<54369ADE.7060201@redhat.com>	<20141009162906.GA25389@calimero.vinschen.de>	<571726.85545.bm@smtp112.sbc.mail.ne1.yahoo.com>	<20141010103446.GJ2681@calimero.vinschen.de>	<CAO1jNwt5UyB9CDKJdotXUND--mg1sY-5Fu+-ZHf2atM5_=HArA@mail.gmail.com>	<CAMCbSMrar1Zu4p6gN=gc8-XqE-8RUTmP3er0ujeN--CHKzCNAQ@mail.gmail.com>	<816144.8551.bm@smtp119.sbc.mail.ne1.yahoo.com>
Date: Fri, 10 Oct 2014 14:13:01 +0200
Message-ID: <CAMCbSMpWKbSVhVu85_02fN3sgWXiFBkUzjOOAJ6+Jxot8X6E=Q@mail.gmail.com>
Subject: Re: Cannot exec() program outside of /bin if PATH is unset
From: Arjen Markus <arjen.markus895@gmail.com>
To: Andrey Repin <cygwin@cygwin.com>
Content-Type: text/plain; charset=UTF-8

Right, that makes sense. There is indeed no way for the package
manager to handle that scenario without external help, such as a PATH
variable that includes the various directories these extra DLLs reside
in.

Regards,

Arjen


2014-10-10 13:22 GMT+02:00  <tednolan@bellsouth.net>:
> In message <CAMCbSMrar1Zu4p6gN=gc8-XqE-8RUTmP3er0ujeN--CHKzCNAQ@mail.gmail.com>
> you write:
>>This might the way the pkgIndex.tcl file for this particular extension
>>has been implemented, but like Jan says, that is not the Tcl way.
>>
>>Here is a sample that illustrates the more acceptable procedure:
>>
>># Tcl package index file, version 1.0
>>
>>if {![package vsatisfies [package provide Tcl] 8.6]} {return}
>>
>>package ifneeded itcl 4.0b7 [list load [file join $dir "itcl40b7.dll"] itcl]
>>package ifneeded Itcl 4.0b7 [list load [file join $dir "itcl40b7.dll"] itcl]
>>
>>The variable "dir" is set by the package management subsystem and the
>>effect is that the _full_ path is constructed before the DLL is
>>actually loaded.
>>
>>Regards,
>>
>>Arjen
>>
>>2014-10-10 13:24 GMT+02:00 Jan Nijtmans <jan.nijtmans@gmail.com>:
>>> 2014-10-10 12:34 GMT+02:00 Corinna Vinschen <corinna-cygwin@cygwin.com>:
>>>> On Oct  9 11:46, tednolan@bellsouth.net wrote:
>>>>> I'm pretty sure I've got some programs loading Tcl extensions that
>>>>> cd into the directory with the extension dlls, load the extension and then
>>>>> change back to where ever they were.
>>>>
>>>> Hmm.  If so, it's quite a weird way to handle this, rather than
>>>> loading the modules with full path.
>>>>
>>>> Is that a Tcl "feature", or is it how certain Tcl apps are implemented?
>>>> I can't really believe the former...
>>>
>>> This is certainly not a Tcl "feature"!  The standard Tcl extension
>>> mechanism always uses the full path simply because Tcl
>>> cannot depend on platform-specific ways to search for
>>> such libraries elsewhere.
>>>
>>> I'm willing to test this;I don't believe such a change
>>> will break anything in my Tcl environment.
>>>
>>> Regards,
>>>        Jan Nijtmans
>
> Hmm,
>
> It's been a while, but I think it is something like the extension is
> a DLL, but it depends on another DLL.  Consider for instance, mysqltcl.
> If you want to deploy that, you need the mysqltcl.dll and the mysql dll,
> so you either have to be in the same dir when you load the extension,
> or put that dir in PATH.
>
> Unfortunately, I can't run a test release on my work machine, or take
> my work progs home.
>
> --
> Problem reports:       http://cygwin.com/problems.html
> FAQ:                   http://cygwin.com/faq/
> Documentation:         http://cygwin.com/docs.html
> Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
>

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple