X-Recipient: archive-cygwin AT delorie DOT com
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=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; 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; s=default; bh=NjWAyLz6
	GnTGtC6jUCvVa5o30cU=; b=so9a4TxJT2SAiNcdux+FdfMN/ees9ePqoyg13p/B
	0i9/GI5zWkXsaJWuDmFlorKd3O0l3oc08+Mjujiale0NL7f12dK5Tc7gBNgmdZZe
	HDC7k72JoD1ifag6O92JE7i+oA/m/Q37UKawZUrDCNVs4t7vAgQ8w2h63KHrV0gs
	lIA=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=4.5 required=5.0 tests=AWL,BAYES_50,FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPAM_URI1,SPF_PASS autolearn=no version=3.3.2
X-HELO: mail-ig0-f180.google.com
MIME-Version: 1.0
X-Received: by 10.42.130.68 with SMTP id u4mr13945362ics.23.1412943181119; Fri, 10 Oct 2014 05:13:01 -0700 (PDT)
In-Reply-To: <816144.8551.bm@smtp119.sbc.mail.ne1.yahoo.com>
References: <54137C7F DOT 1040507 AT redhat DOT com>	<541415B1 DOT 8090500 AT t-online DOT de>	<541698CC DOT 7090802 AT lysator DOT liu DOT se>	<5416F946 DOT 7010905 AT t-online DOT de>	<20141008134106 DOT GF29235 AT calimero DOT vinschen DOT de>	<5435714D DOT 6060206 AT t-online DOT de>	<20141009100317 DOT GI29235 AT calimero DOT vinschen DOT de>	<54369ADE DOT 7060201 AT redhat DOT com>	<20141009162906 DOT GA25389 AT calimero DOT vinschen DOT de>	<571726 DOT 85545 DOT bm AT smtp112 DOT sbc DOT mail DOT ne1 DOT yahoo DOT com>	<20141010103446 DOT GJ2681 AT calimero DOT vinschen DOT de>	<CAO1jNwt5UyB9CDKJdotXUND--mg1sY-5Fu+-ZHf2atM5_=HArA AT mail DOT gmail DOT com>	<CAMCbSMrar1Zu4p6gN=gc8-XqE-8RUTmP3er0ujeN--CHKzCNAQ AT mail DOT gmail DOT com>	<816144 DOT 8551 DOT bm AT smtp119 DOT sbc DOT mail DOT ne1 DOT yahoo DOT 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 DOT markus895 AT gmail DOT com>
To: Andrey Repin <cygwin AT cygwin DOT com>
Content-Type: text/plain; charset=UTF-8
X-IsSubscribed: yes

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 AT bellsouth DOT net>:
> In message <CAMCbSMrar1Zu4p6gN=gc8-XqE-8RUTmP3er0ujeN--CHKzCNAQ AT mail DOT gmail DOT 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 DOT nijtmans AT gmail DOT com>:
>>> 2014-10-10 12:34 GMT+02:00 Corinna Vinschen <corinna-cygwin AT cygwin DOT com>:
>>>> On Oct  9 11:46, tednolan AT bellsouth DOT 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