Lets keep Microsoft out of this, this is a Pd and Pd externals issue.

Deken is a primitive tool that just download and extracts, very useful, the problem comes because w32 Deken pkgs were wrongly/naively packed.

How does other Os handle Deken package dependencies? 

There are more than 120 w32 deken pkgs, many of them not fully operational in a 2016 pd situation, I mean without pd-extended installed.

Following IOhannes idea that a deken pkg must be self operational it must contain the externals, the help patches and if needed its dependencies (pthread implementation and other .dlls)

How we update all w32 Deken pkgs?

To: pd-list@lists.iem.at
From: zmoelnig@iem.at
Date: Tue, 12 Jul 2016 09:41:11 +0200
Subject: Re: [PD] w32 Deken package issues.

On 2016-07-11 16:40, Colet Patrice wrote:
> Ok I get it, that's quite cool but, so there will be copies of the same
> lib into each external folder needing it?
 
yes. that's the microsoft way to ship dependencies.
i think it's best to stick with the microsoft way when using w32 (and
even better to not having to use w32).
 
fgsdm
IOhannes
 

_______________________________________________ Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list